MCP Dynamic Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| tools-dir | Yes | Directory where the Python tool files are located |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_toolB | Create a new dynamic MCP tool by writing Python code to a file |
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 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly distinct and singular.
Naming is perfectly consistent as there is only one tool. The verb_noun pattern 'write_tool' is clear and follows a logical structure.
The single tool is appropriate for the core functionality of creating a dynamic tool, but the server's purpose suggests a need for additional management tools (e.g., list, delete), making the count feel slightly thin.
The tool set covers creation only, lacking any lifecycle operations like listing, updating, or deleting dynamic tools. This leaves significant gaps for agents needing to manage tools beyond creation.