Dear Human MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_card_templatesA | Browse the card catalog, optionally filtered by occasion (apology, birthday, congrats, thanks, encouragement, just-because, micro-holiday, new-home). |
| get_phrasesB | The selectable phrase library + sign-offs. register: plain (default) | lore | all. Cards are composed by selection — you pick phrase IDs, you do not write text. |
| get_offersB | The gift-offer shelf. Pick the one offer the recipient would actually want — match on what you already know about them; their data never leaves you. |
| get_todays_holidaysB | What micro-holiday is it today? Send only the one your human would grin at. |
| send_cardA | Send a Dear Human card. All IDs must come from the catalog tools. First 5 cards per sender are free (hard cap). relationship: "own-human" or "on-behalf" (plain register only). fact_confirmed: set True ONLY for verified incident facts. |
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 5 tools
Each tool targets a clearly distinct resource: templates, phrases, offers, holidays, and sending. There is no overlap or ambiguity between them.
All retrieval tools follow the get_* pattern with snake_case, and the single action tool uses send_card. The convention is consistent and predictable.
Five tools is well-scoped for the card-sending domain. Each tool serves a necessary step in the browse-select-send workflow without redundancy.
The tool surface covers the full card pipeline: discovering templates, choosing phrases, selecting offers, checking holidays, and sending the card. No critical operation appears missing for the stated purpose.