decoder-3am-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 |
|---|---|
| classify_sleep_causeD | – |
| get_cause_infoD | – |
| list_causesD | – |
| get_decoder_urlD | – |
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 4 tools
Each tool targets a distinct operation: classifying a cause, listing causes, retrieving cause info, and fetching the decoder URL. There is slight potential for confusion between list_causes and get_cause_info, but the list vs. single-item distinction is clear enough.
All four tools follow a consistent verb_noun snake_case pattern: classify_, list_, get_, get_. This makes the set predictable and easy to navigate.
Four tools is a well-scoped size for a focused decoder utility. Each tool appears to serve a distinct purpose without unnecessary bloat or thinness.
The set covers the apparent core domain: listing causes, retrieving details, classifying, and accessing the decoder URL. A possible gap is lack of any tool for submitting or updating sleep data, but for a small decoder utility this may be intentional.