MCP Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (when TRANSPORT=http) | 4657 |
| DEBUG | No | Enable debug mode and utils_debug tool | false |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_symbolA | Find and extract symbol block by name from files, supports a lot of file formats (like TS, JS, GraphQL, CSS and most that use braces for blocks). Uses streaming with concurrency control for better performance |
| insert_textA | Insert or replace text at precise line ranges in files
|
| os_notificationB | Send OS notifications using native notification systems. |
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 3 tools
Each tool has a clearly distinct purpose: insert_text for line-based file editing, os_notification for system alerts, and read_symbol for symbol extraction. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent snake_case pattern with a verb_noun structure (insert_text, os_notification, read_symbol). This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the set feels thin for a general-purpose 'MCP Tools' server, potentially lacking coverage for common operations like file reading or deletion. However, the tools are well-defined, so it's borderline but not severely mismatched.
The tool set has significant gaps for a file and system operations domain: there is no tool for reading file contents (only symbol extraction), deleting files, or basic file management. This incompleteness will likely cause agent failures in broader workflows.