| name | mcp-tool-change |
| description | Use when adding, renaming, or removing an MCP tool in gtex-link. Walks through facade registration, profiles, descriptions, tests. |
MCP tool change
Use this skill when changing the MCP tool surface (additions, renames, removals, description rewrites).
Checklist
- Decide tool category. Reference (
gene, transcript, feature), expression (median, top, individual), or ChatGPT search/fetch.
- Register in the right file.
- Reference:
gtex_link/mcp/tools/reference.py
- Expression:
gtex_link/mcp/tools/expression.py
- ChatGPT:
gtex_link/mcp/tools/search_fetch.py
- Tune the description. Write for an AI client picking a tool — what does it do, when to use it, what does the input/output look like, what does it NOT do.
- Profile assignment. Open
gtex_link/mcp/profiles.py and decide if the tool belongs in full, lite, or both.
- Output validation. Confirm
output_validation.py will catch malformed outputs.
- Error mapping. If the tool can raise a new exception class, add a mapping in
gtex_link/mcp/errors.py.
- Tests.
- Add tests under
tests/test_mcp/ covering the tool's behavior, profile presence, and error masking.
- Run
make test -k <tool_name>.
- Preserved names. Existing tool names are part of the public contract; renaming requires a
CHANGELOG.md entry and a migration note.
- CI. Run
make ci-local.