Skip to main content
Glama

get_heart_rates_summary

Read-only

Retrieve a compact heart rate summary with essential metrics for a specified date, enabling quick daily health checkups and efficient LLM integrations.

Instructions

Get heart rate summary with essential metrics (lightweight version)

    Returns a compact summary (~500 bytes) instead of full time-series data (~25KB).
    Ideal for daily health checkups and LLM integrations.

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_heart_rates_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context by quantifying the response (~500 bytes vs ~25KB of time-series data), which helps an agent budget context. Auth requirements, rate limits, and what happens with future/invalid dates are unaddressed.

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 key differentiator (lightweight summary vs full payload) is front-loaded in the first two lines. The 'Args:' block is docstring boilerplate that carries only one short detail, but overall length is proportionate and no sentence is wasteful.

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 single-parameter read tool with read-only annotations, the definition covers purpose, size/payload expectations, and date format — enough to invoke it correctly. Missing only edge-case behavior (empty dates, timezone) and explicit sibling routing, which are minor for this complexity.

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 0%, so the sole parameter 'date' has no schema-level documentation. The description compensates by specifying the YYYY-MM-DD format, which is the minimum needed to call correctly, but says nothing about timezone handling, date bounds, or behavior for dates with no recorded data.

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?

States a specific verb and resource (get heart rate summary) and defines scope: a compact metrics summary rather than a time series. The contrast with 'full time-series data (~25KB)' implicitly distinguishes it from get_heart_rates, though that sibling is never named, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

"Ideal for daily health checkups and LLM integrations" gives concrete usage context, and the size contrast tells an agent to prefer this when the full series is unnecessary. It stops short of an explicit rule such as 'use get_heart_rates when you need per-second readings,' so the exclusion must be inferred.

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