Skip to main content
Glama

list_ecgs

Read-onlyIdempotent

Lists every ECG your Apple Watch recorded, newest first, with time, classification, symptoms status, average heart rate, sampling frequency, algorithm version, device, and voltage file availability.

Instructions

Every ECG the Watch recorded, newest first: time, classification, symptoms status, average heart rate, sampling frequency, algorithm version, device, and whether a voltage file sits next to it.

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_ecgs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and idempotentHint, so safety is covered; the description adds the concrete return shape and the 'newest first' ordering guarantee. It also implies no pagination by saying 'Every' ECG, which is useful behavior context. It stops short of stating behavior with an empty result set or any size limits.

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?

A single sentence that front-loads the resource and ordering before enumerating fields. Every clause carries information; nothing is repeated from the name or annotations.

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?

With no parameters and no output schema, the description carries the return-value burden and does it well by enumerating the fields. Minor gaps remain, such as what an empty list looks like and what the classification or symptoms-status values can be, but the essentials are present.

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?

The tool takes no parameters, so there is nothing to disambiguate and the baseline applies. The description instead spends its space on output fields, which is the right use of text for a zero-argument tool.

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 resource ('Every ECG the Watch recorded') with ordering and a field inventory, so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like get_vitals, but the resource is distinct enough that confusion is unlikely.

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 word 'Every' signals an unfiltered bulk listing with no parameters, which suggests it is the broad-retrieval option. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for filtered or detail-level lookups.

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