Skip to main content
Glama

set_blood_pressure

Record systolic, diastolic, and pulse values in Garmin Connect to log a blood pressure reading, with optional notes for context.

Instructions

Set blood pressure values

    Args:
        systolic: Systolic pressure (top number)
        diastolic: Diastolic pressure (bottom number)
        pulse: Pulse rate
        notes: Optional notes
    

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>",
      "pulse": "<pulse>"
    },
    "name": "set_blood_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
pulseYes
systolicYes
diastolicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that: it never says whether each call appends a new reading or replaces the latest one (important given idempotent=false), nor whether existing notes survive a re-set. Units and validation ranges are also absent.

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 one-line purpose is front-loaded and the per-argument list is easy to scan; nothing is redundant or buried. The Args formatting reads as generated boilerplate rather than prose, but it wastes no words.

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?

For a write tool with four parameters, no output schema, and zero schema-level descriptions, the definition should specify units, sensible ranges, and what happens on repeat calls. None of that is present, so an agent could easily submit values with wrong units or misunderstand the overwrite semantics.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it only partly does. 'Systolic pressure (top number)' and 'Diastolic pressure (bottom number)' are minimally clarifying, but no units (mmHg), plausible ranges, or pulse units (bpm) are given, and 'notes: Optional notes' merely restates the schema's default=null.

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?

'Set blood pressure values' names a specific verb (set) and resource (blood pressure), clearly distinguishing it from the read-only sibling get_blood_pressure even though that sibling is never named. The Args block enumerates the records' fields, so an agent knows what data this writes.

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 get_blood_pressure, nor on prerequisites such as whether a reading needs to exist first or whether calling it repeatedly overwrites the previous entry. Usage is only implied by the verb 'set'.

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