Skip to main content
Glama

get_activity_hr_in_timezones

Read-only

Retrieves heart rate data split by time zone for a specific Garmin activity, helping compare effort across locations or travel.

Instructions

Get heart rate data in different time zones for an activity

    Args:
        activity_id: ID of the activity to retrieve heart rate time zone data for
    

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_hr_in_timezones"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond them: it does not explain what the time-zone breakdown contains, whether all data is returned at once, or how the result is structured.

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?

Two short lines, front-loaded with the core purpose, with no redundant or wasteful wording. The boilerplate 'Args:' block is the only slightly mechanical element.

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

Completeness3/5

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

For a simple one-parameter read tool with no output schema and full annotation coverage, this is close to adequate, but it never conveys what the returned time-zone HR data looks like or the applicable time-zone semantics, which is the one thing the name cannot tell an agent.

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?

With schema description coverage at 0%, the description must carry parameter meaning, and it does give a brief gloss ('ID of the activity to retrieve heart rate time zone data for'). However, it omits the anyOf integer-or-string nature of activity_id and its format (e.g., Garmin activity ID), leaving a gap.

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 data in different time zones for an activity, which an agent can distinguish from the sibling get_activity_power_in_timezones (HR vs power). It does not explicitly name or contrast the sibling, so it falls short of 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 instead of get_activity, get_activity_fit_data, or the power-in-timezones variant, and no prerequisites or exclusions are stated. The agent must infer usage from the name alone.

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