Get your daily breathing rate data from Garmin Connect, including waking, sleeping, highest, and lowest breaths per minute.
Breathing rate for a day: waking, sleeping, highest and lowest breaths per minute.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds context about the metrics returned but does not disclose date handling, output format, or potential errors. Since annotations cover safety, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the purpose. Every word contributes to meaning, with no unnecessary detail. It is appropriately sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the low complexity (one optional parameter) and presence of an output schema, the description lacks essential invocation details like date format and null semantics. An agent cannot reliably construct a correct call without external knowledge, making it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for parameter meaning. It implies the 'date' parameter selects the day but does not specify the format (e.g., YYYY-MM-DD) or explain what null default means. The agent is left guessing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (breathing rate) and the specific metrics (waking, sleeping, highest, lowest) for a day. It distinguishes from siblings like garmin_heart_rate by focusing on respiration. However, it lacks an explicit verb like 'get' or 'retrieve', so it's not a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or reference sibling tools like garmin_hrv or garmin_stress. The agent must infer usage solely from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.