Skip to main content
Glama

get_blood_pressure

Retrieve blood pressure readings from Garmin Connect for a specified date range to monitor systolic and diastolic trends.

Instructions

Get blood pressure readings over a date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format

Implementation Reference

  • The handler function that executes the getBloodPressure API call, sending a request to the blood pressure endpoint with start and end dates.
    async getBloodPressure(startDate: string, endDate: string): Promise<unknown> {
      return this.request(`${BLOOD_PRESSURE_ENDPOINT}/${startDate}/${endDate}`);
    }
  • Input schema (dateRangeParamSchema) defining startDate and endDate as required date strings for the tool.
    export const dateRangeParamSchema = z.object({
      startDate: dateString.describe('Start date in YYYY-MM-DD format'),
      endDate: dateString.describe('End date in YYYY-MM-DD format'),
    });
  • Registration of the 'get_blood_pressure' tool using server.registerTool with description and input schema.
    server.registerTool(
      'get_blood_pressure',
      {
        description: 'Get blood pressure readings over a date range',
        inputSchema: dateRangeParamSchema.shape,
      },
      async ({ startDate, endDate }) => {
        const data = await client.getBloodPressure(startDate, endDate);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Constant defining the blood pressure API endpoint path '/bloodpressure-service/bloodpressure/range'.
    export const BLOOD_PRESSURE_ENDPOINT = '/bloodpressure-service/bloodpressure/range';
Behavior3/5

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

No annotations are provided, so the description must carry behavioral transparency. 'Get' implies read-only, but the description does not explicitly confirm non-destructive behavior or mention any constraints like pagination or authentication. It is adequate but minimal.

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?

The description is a single sentence with no redundant words. It is front-loaded and efficiently conveys the tool's core function.

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

Completeness2/5

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

The tool has no output schema, so the description should hint at the return structure (e.g., systolic, diastolic, timestamp). It lacks any explanation of what data is returned, making it incomplete for an agent to understand the tool's output.

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 both parameters having clear descriptions (date format). The description adds no additional semantics beyond 'over a date range', which is already conveyed by the parameter names. Baseline of 3 is appropriate.

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?

The description clearly states the tool retrieves blood pressure readings over a date range, using the verb 'get' and resource 'blood pressure readings'. It strongly distinguishes from the sibling 'set_blood_pressure'.

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?

The description implies use when needing blood pressure data in a time period, but does not explicitly state when to use it versus alternatives like 'set_blood_pressure' or other health data retrieval tools. No exclusions are given.

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