adhd-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_contextB | Estimate or accept reported context window usage %. Call before format_status_footer when IDE ring % is unknown. |
| format_status_footerB | Build mandatory ADHD reply footer. Pass THIS TURN char counts for 本轮 tok (user + tools + reply). |
| check_readinessA | Returns whether understanding ≥95% — code edits forbidden when ready=false. |
| qa_session_startB | Create adhd/sessions/YYYY-MM-DD-slug.md when starting Q&A for a task. |
| qa_session_appendB | Append one Q&A entry to session file. Ask only ONE question per chat turn. |
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 has a clearly distinct purpose: context estimation, footer formatting, readiness check, session creation, and session appending. No two tools could be confused for one another.
All tool names follow a consistent verb_noun pattern (estimate_context, format_status_footer, check_readiness, qa_session_start, qa_session_append). Perfectly predictable.
Five tools is well-scoped for this niche server. Each tool earns its place and covers a specific step in the workflow without redundancy.
The surface fully covers the intended domain: context awareness, mandatory formatting, readiness gating, and Q&A session lifecycle. No obvious gaps for the stated purpose.