mcp-dev-record
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_template_listA | 获取可用的开发记录模板列表。返回包含模板名称、文件名和描述的结构化数据。返回的 templates 数组中每个模板都有 templateName 字段，这是后续调用 get_template_detail 时必需的参数。使用此工具来发现可用的模板，然后使用返回的 templateName 来获取具体模板内容。 |
| get_template_detailA | 获取指定模板的详细内容。templateName 参数必须使用 get_template_list 返回的 templates 中的 templateName 值。这确保了参数的准确性和一致性。返回模板的完整内容，可用于创建新的开发记录文档。如果模板不存在，会返回明确的错误信息。 |
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 2 tools
The two tools have clearly distinct purposes: get_template_list retrieves a list of available templates with metadata, while get_template_detail fetches the detailed content of a specific template. There is no overlap or ambiguity between them, as one is for discovery and the other for content retrieval.
Both tools follow a consistent verb_noun pattern (get_template_list and get_template_detail), using the same verb 'get' and a clear noun structure. This makes the naming predictable and easy to understand across the tool set.
With only 2 tools, the server feels thin for a development record domain, as it lacks operations like creating, updating, or deleting templates or records. While the tools cover basic retrieval, the scope seems limited, potentially requiring agents to work around missing functionality.
The tool surface is significantly incomplete for a development record system. It only provides read operations (list and detail retrieval) with no ability to create, update, or delete templates or records. This leaves obvious gaps that could cause agent failures when trying to perform full lifecycle management.