Skip to main content
Glama
Sign In

Wellness Project

by ai.wellnessproject
OverviewDiscussionsAdmin

list_blood_pressure_readings

Read-onlyIdempotent

Read individual timestamped systolic/diastolic blood pressure pairs imported from connected health sources, including Apple Health and Health Connect. Use when the user asks for actual BP readings, their times, sources, or changes within a day. Use list_wearable_data for daily summaries. Dates use the user's local timezone; defaults to the last seven calendar days, maximum 31 days. Returns at most 400 observations; narrow the date range if exceeded. Only recorded pairs are shown, with no interpolation. Missing measurements do not imply normal blood pressure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_blood_pressure_readings"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoInclusive local date, YYYY-MM-DD. Default: today.
start_dateNoInclusive local date, YYYY-MM-DD. Default: six days ago.

Output Schema

NameRequiredDescriptionDefault
resultYesHuman-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower, yet the description still adds substantial context: local-timezone date interpretation, a 7-day default, a 31-day ceiling, and a 400-observation cap with the instruction to narrow the range. It also warns that only recorded pairs are returned with no interpolation and that missing measurements do not imply normal blood pressure — a meaningful data-integrity caveat.

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?

Five sentences, each carrying distinct information — scope, trigger, alternative, date/limit constraints, and data caveat — with the core purpose front-loaded. There is mild overlap with schema-stated defaults, but no sentence is filler.

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

Completeness5/5

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

An output schema exists, so return-shape explanation is unnecessary; the description instead covers what an agent actually needs to call it correctly: trigger conditions, sibling routing, date semantics, result caps, and the no-interpolation caveat. Nothing material is missing for a two-parameter read tool.

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 100% and the schema already documents both date parameters and their defaults, so the baseline is 3. The description adds genuinely new meaning beyond the schema: dates are interpreted in the user's local timezone and the span is capped at 31 days, which affects how an agent should construct the start_date/end_date pair.

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?

Opens with a specific verb and resource: 'Read individual timestamped systolic/diastolic blood pressure pairs imported from connected health sources.' It also names the data origin (Apple Health, Health Connect) and implicitly distinguishes itself from the daily-summary sibling, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the triggering user intents ('asks for actual BP readings, their times, sources, or changes within a day') and names the alternative with its condition: 'Use list_wearable_data for daily summaries.' That is both a when-to-use and a when-to-use-something-else rule.

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

All Wellness Project toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources