Skip to main content
Glama

get_respiration

Retrieve daily respiration rate data for a specified date. Useful for monitoring breathing patterns and respiratory health trends.

Instructions

Get daily respiration rate data throughout the day. Single date; for ranges use get_respiration_range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • Tool registration and handler for 'get_respiration'. Registers the tool with MCP server, accepts an optional date parameter (defaults to today), calls client.getRespiration(), and returns the data as JSON.
    server.registerTool(
      'get_respiration',
      {
        description: 'Get daily respiration rate data throughout the day. Single date; for ranges use get_respiration_range',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getRespiration(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
  • Input schema for the get_respiration tool. Defines an optional 'date' parameter in YYYY-MM-DD format (defaults to today).
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Client method getRespiration() - the low-level handler that calls the Garmin API endpoint. Uses DAILY_RESPIRATION_ENDPOINT and defaults to today's date if none provided.
    async getRespiration(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${DAILY_RESPIRATION_ENDPOINT}/${resolvedDate}`);
    }
  • API endpoint constant DAILY_RESPIRATION_ENDPOINT mapping to '/wellness-service/wellness/daily/respiration'.
    export const DAILY_RESPIRATION_ENDPOINT = '/wellness-service/wellness/daily/respiration';
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions data is retrieved 'throughout the day' but lacks details on output format, resolution, or any behavioral constraints. Basic but adequate for a simple read tool.

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

Conciseness5/5

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

Two concise sentences with no filler. The first sentence states purpose, the second provides usage guidance. Front-loaded and efficient.

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

Completeness4/5

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

For a simple tool with one optional parameter and no output schema, the description covers essential aspects: what it does and when to use it. The sibling list provides context for differentiation. Minor gap: no mention of return format or potential limitations.

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

Parameters3/5

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

Schema coverage is 100% with one parameter (date) documented. Description adds context about daily data but does not enhance semantic understanding beyond the schema. Baseline score of 3 applies.

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

Purpose5/5

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

Description clearly states the tool retrieves daily respiration rate data for a single date, with a specific verb and resource. It distinguishes from the sibling get_respiration_range by explicitly noting scope.

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

Usage Guidelines5/5

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

Explicitly states 'Single date; for ranges use get_respiration_range', providing clear when-to-use and when-not-to-use guidance, along with an alternative sibling tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server