Skip to main content
Glama

garmin_add_blood_pressure

Record a blood-pressure reading in Garmin Connect with systolic and diastolic values, plus optional timestamp, pulse, and notes.

Instructions

Record a blood-pressure reading (mmHg).

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": {
      "systolic": "<systolic>",
      "diastolic": "<diastolic>"
    },
    "name": "garmin_add_blood_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNo'YYYY-MM-DD HH:MM', 'HH:MM' for today, or omit for now
notesNo
pulseNo
systolicYes
diastolicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds only the unit of measurement and says nothing about duplicate handling, required account state, whether the write can be corrected or deleted later, or what the call returns.

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

Conciseness3/5

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

The single sentence is front-loaded and wastes no words, but for a 5-parameter mutation tool it is too terse to count as appropriately sized. Efficiency here tips into under-specification rather than disciplined conciseness.

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?

With five parameters, 20% schema coverage, no output schema, and no annotations covering anything beyond safety flags, the description leaves substantial gaps. An agent cannot tell what a successful response looks like or what units/limits apply to pulse and notes.

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 description coverage is 20% — only 'when' is documented, with a useful format hint. The description partially compensates by declaring mmHg units for systolic and diastolic, but gives no valid ranges, no explanation of pulse/notes, and no mention that systolic and diastolic are required.

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?

The description names a specific verb (Record) and resource (blood-pressure reading) and supplies the unit (mmHg), so an agent can distinguish it from siblings like garmin_add_weigh_in or garmin_add_body_composition. It does not explicitly name those siblings, keeping it below a 5.

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

Usage Guidelines2/5

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 versus garmin_add_body_composition, garmin_add_weigh_in, or garmin_womens_health, and no statement of prerequisites such as an authenticated Garmin session. The agent must infer usage entirely from the tool name.

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