dynamic-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RULES_PATH | No | Optional absolute path to the rules directory. Defaults to '.agent/rules' in the current working directory. |
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 |
|---|---|
| get_context_for_fileA | Retrieves coding guidelines and context based on the file path provided. Call this before editing code. |
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
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly described.
With a single tool, naming consistency is not an issue. The name 'get_context_for_file' follows a clear snake_case verb_noun pattern.
A single tool is thin for most servers, but may be acceptable if the server's sole purpose is to retrieve context for a file path. However, it feels minimal.
The server covers only one operation (getting context). Missing operations like listing contexts, setting contexts, or clearing contexts create significant gaps for a complete context management surface.