Skip to main content
Glama

get_catalog

Read-onlyIdempotent

Lists every HealthKit type with athlete data, including 90-day sample counts, first/last dates, export locations, and coverage gaps against known identifiers.

Instructions

What Health holds for this athlete: every HealthKit type with has_data, sample count over 90 days, first and last date and where the app exported it, plus the coverage check against the identifier list this build knows (types with data not exported, unknown types with data).

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": "get_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the 90-day counting window, the notion of an export destination per type, and that the response includes a coverage check flagging types with data that were not exported and unknown types with data. It does not mention response size or performance for athletes with many types.

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?

It is a single dense sentence that front-loads the core answer ("What Health holds for this athlete") before enumerating payload fields. Every clause carries information, though the nested parenthetical listing makes the coverage-check portion slightly hard to parse on first read.

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 output schema and no parameters, the description bears the full burden of explaining return values, and it does so field by field. What is missing is only the container shape (list vs. keyed object) and rough result size, which are minor for a zero-argument 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?

The tool takes no parameters and the schema confirms an empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly implies a whole-athlete scope with no filtering options.

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 names the resource concretely ("every HealthKit type" for "this athlete") and enumerates the fields returned: has_data, 90-day sample count, first/last date, export location, and a coverage check. It is clearly an inventory/discovery tool rather than a data-series reader, which distinguishes it in spirit from siblings like get_vitals or get_day, though it never names an alternative explicitly.

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?

There is no explicit when-to-use statement, no prerequisite conditions, and no named alternative. Usage is only implied by content: the coverage check against "the identifier list this build knows" signals a diagnostic/discovery role, so an agent can infer it should be called before deeper queries, but must do the inferring itself.

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