Skip to main content
Glama

判讀居家血壓

check_home_blood_pressure
Read-onlyIdempotent

判讀居家血壓(依台灣 2022 高血壓指引 130/80),回傳平均、分級、是否達危急值與 722 量測方法。readings 例:128/82,134/86(最多 6 筆)。

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": {
      "readings": "<readings>"
    },
    "name": "check_home_blood_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
readingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real value beyond them: the specific clinical guideline and threshold used, the list of returned judgments (average, grade, critical value, 722 method), and a hard input limit of 6 readings. It does not say how invalid or malformed readings are handled, which would complete the picture.

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?

One dense sentence carries the rule set, the return contents, and the limit; the example follows immediately. No filler, and the most decision-relevant material (guideline threshold) is front-loaded.

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 one-parameter read-only tool with no output schema, the description is nearly sufficient: it names the reference standard and enumerates the returned judgments, so the agent knows what to expect. Minor gaps are error/edge-case behavior for out-of-range or unparseable readings.

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

Parameters4/5

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

Schema coverage is 0% for the single `readings` string, so the description must carry the semantics, and it does: an explicit example ('128/82,134/86') establishes the separator and systolic/diastolic ordering, and 'max 6 entries' documents a constraint the schema lacks. It stops short of stating units, valid ranges, or behavior on malformed input.

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 gives a specific verb (判讀 / interpret) and resource (居家血壓 / home blood pressure), plus the exact rule set it applies (Taiwan 2022 guideline, 130/80 threshold). This clearly separates it from blood-glucose or screening siblings without naming them, but there is no explicit sibling callout.

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?

Usage is only implied: the agent infers this is the tool for entering home BP readings. There is no statement of when to prefer it over other check_* tools, no prerequisites (e.g., readings should be from home, resting measurements), and no exclusion conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources