Skip to main content
Glama

get_respiration_summary

Read-only

Retrieve essential respiration metrics for a specific date in a compact summary, avoiding large time-series data.

Instructions

Get respiration summary with essential metrics (lightweight version)

    Returns a compact summary (~300 bytes) instead of full time-series data (~20KB).

    Args:
        date: Date in YYYY-MM-DD format
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_respiration_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context: a ~300-byte response versus ~20KB for full data, which tells the agent the token cost of calling it. It does not disclose which metrics are included, the data source, or unit conventions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the payload-size distinction, and short overall. The 'Args:' block is leftover docstring formatting rather than prose, and 'respiration summary ... summary' repeats itself slightly, but nothing is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only source of return-value information, and 'essential metrics' does not say which metrics (breathing rate, variability, etc.) come back. Combined with sparse annotations and an undocumented parameter, it is adequate for calling the tool but not for interpreting its output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single property 'date' has no description in the schema, so the description must compensate. It does by specifying the required YYYY-MM-DD format, which is the one detail an agent could otherwise get wrong for this parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get respiration summary) and qualifies it as the 'lightweight version' returning essential metrics. The contrast with 'full time-series data (~20KB)' distinguishes it in spirit from get_respiration_data, though that sibling is never named, leaving the agent to infer the pairing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the size contrast: use this when a compact summary is sufficient rather than full time-series data. There is no explicit statement of when to prefer get_respiration_data, no exclusions, and no prerequisites, so the routing decision is largely left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools