Skip to main content
Glama

set_blood_pressure

Record blood pressure measurements with systolic, diastolic, and pulse values for monitoring in Garmin Connect.

Instructions

Record a blood pressure measurement with systolic, diastolic, and pulse

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
systolicYesSystolic pressure (mmHg)
diastolicYesDiastolic pressure (mmHg)
pulseYesPulse rate (bpm)
timestampNoMeasurement timestamp in ISO 8601 format. Defaults to now
notesNoOptional notes about the measurement

Implementation Reference

  • The tool registration and handler function for 'set_blood_pressure'. It registers the tool with server, defines description and input schema, and the handler calls client.setBloodPressure().
    server.registerTool(
      'set_blood_pressure',
      {
        description: 'Record a blood pressure measurement with systolic, diastolic, and pulse',
        inputSchema: setBloodPressureSchema.shape,
      },
      async ({ systolic, diastolic, pulse, timestamp, notes }) => {
        const data = await client.setBloodPressure(systolic, diastolic, pulse, timestamp, notes);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Registration of the 'set_blood_pressure' tool on the MCP server via server.registerTool().
    server.registerTool(
      'set_blood_pressure',
      {
        description: 'Record a blood pressure measurement with systolic, diastolic, and pulse',
        inputSchema: setBloodPressureSchema.shape,
      },
      async ({ systolic, diastolic, pulse, timestamp, notes }) => {
        const data = await client.setBloodPressure(systolic, diastolic, pulse, timestamp, notes);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The SetBloodPressureDto type definition and the setBloodPressureSchema Zod validation schema defining systolic (max 300), diastolic (max 200), pulse (max 300), timestamp (optional ISO 8601), and notes (optional).
    export type SetBloodPressureDto = {
      systolic: number;
      diastolic: number;
      pulse: number;
      timestamp?: string;
      notes?: string;
    };
    
    export const setBloodPressureSchema = z.object({
      systolic: z.number().positive().max(300).describe('Systolic pressure (mmHg)'),
      diastolic: z.number().positive().max(200).describe('Diastolic pressure (mmHg)'),
      pulse: z.number().positive().max(300).describe('Pulse rate (bpm)'),
      timestamp: z
        .string()
        .optional()
        .describe('Measurement timestamp in ISO 8601 format. Defaults to now'),
      notes: z.string().optional().describe('Optional notes about the measurement'),
    });
  • The client method setBloodPressure() that makes the actual HTTP POST request to the Garmin API endpoint with systolic, diastolic, pulse, measurementTimestampGMT, notes, and sourceType='manual'.
    async setBloodPressure(
      systolic: number,
      diastolic: number,
      pulse: number,
      timestamp?: string,
      notes?: string,
    ): Promise<unknown> {
      const ts = timestamp ?? new Date().toISOString();
      return this.request(SET_BLOOD_PRESSURE_ENDPOINT, {
        method: 'POST',
        body: {
          systolic,
          diastolic,
          pulse,
          measurementTimestampGMT: ts,
          notes: notes ?? null,
          sourceType: 'manual',
        },
      });
    }
  • The API endpoint constant SET_BLOOD_PRESSURE_ENDPOINT = '/bloodpressure-service/bloodpressure'.
    export const SET_BLOOD_PRESSURE_ENDPOINT = '/bloodpressure-service/bloodpressure';
Behavior2/5

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

No annotations exist, so the description must cover behavioral traits. It only states 'Record' without explaining side effects (e.g., overwriting, limits) or return values. No output schema provided.

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?

The description is a single clear sentence with no redundancy. Could be slightly more informative but remains concise.

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?

Given the tool's simplicity (recording a measurement), the description is adequate but incomplete. Missing details like timestamp format or notes, though schema covers them.

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?

All parameters already have descriptions in the input schema (100% coverage). The description adds no new meaning beyond listing them, meeting baseline but not exceeding.

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 'Record a blood pressure measurement', specifying the action and resource. It distinguishes from sibling tools like get_blood_pressure, which retrieves data instead of recording.

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 when to use (to record a measurement) but provides no explicit guidance on alternatives or when not to use. No mention of editing existing records or prerequisites.

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