pxt-anzu-diary-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIARY_API_BASE | No | Base URL for the diary API | http://localhost:8000/api |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add-noteC | 日記を追加します |
| get-noteA | 指定された年の日記を取得します |
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, add-note and get-note, are clearly distinct: one creates a diary entry and the other retrieves one. No overlap or ambiguity exists between them.
Both tool names follow the same verb_noun pattern with a hyphen separator: add-note and get-note. This is fully consistent and predictable.
With only 2 tools, the server feels borderline thin. While each tool has a clear purpose, the count is at the low end of what is considered reasonable for a domain-specific server.
The server covers create and get operations only, missing update, delete, and list functionality. These are notable gaps for a diary management server, though the core add/retrieve flow is present.