MCP-TY
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_projectB | Initialize ty for a Python project. Must be called first. |
| search_symbolC | Search symbols (classes, functions, variables) across the project. |
| list_file_symbolsC | List all symbols defined in a file. |
| read_codeB | Read file content, optionally by line range (1-based). |
| read_contextC | Read code around a specific line with context. |
| stop_projectC | Stop ty and release resources. |
| get_definitionC | Go to definition of symbol at position (1-based). |
| find_usagesB | Find all references to symbol at position (1-based). |
| get_type_infoB | Get type information for symbol at position (1-based). |
| get_diagnosticsB | Get type errors and warnings for a file. |
| get_completionsB | Get code completion suggestions at position (1-based). |
| analyze_fileC | Analyze a Python file: get structure and diagnostics summary. |
| safe_renameB | Rename symbol across project. Set apply=True to execute. |
| get_code_actionsB | Get available quick fixes and refactorings at position (1-based). |
| apply_code_actionC | Apply a code action by index (from get_code_actions). |
| get_edit_previewC | Preview changes a code action would make. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose with no overlap: analyze_file examines structure, get_completions provides suggestions, safe_rename handles renaming, etc. The descriptions make it easy to differentiate between analysis, navigation, editing, and project management functions.
All tools follow a consistent verb_noun or verb_noun_noun pattern (e.g., analyze_file, get_completions, safe_rename). The naming is uniform throughout, using snake_case exclusively with clear action-oriented verbs like get, find, apply, and list.
With 16 tools, the count is slightly high but reasonable for a comprehensive Python code analysis server. It covers diagnostics, navigation, refactoring, and project setup, though it might benefit from slight consolidation in areas like read_code and read_context.
The toolset provides complete coverage for Python code analysis and editing: it includes project initialization (start_project), file reading (read_code), diagnostics (get_diagnostics), navigation (get_definition, find_usages), refactoring (safe_rename, apply_code_action), and cleanup (stop_project). No obvious gaps exist for its intended domain.