Skip to main content
Glama

discover

Read-onlyIdempotent

Browse Garmin data domains, search available operations, or retrieve one operation's exact parameter schema and example for offline API discovery.

Instructions

Offline discovery: browse domains, search operations, or retrieve one operation's exact parameter schema and example.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
domainNo
offsetNo
operationNo

Output Schema

NameRequiredDescriptionDefault
dataYes
errorNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, destructive=false and openWorldHint=false, so the safety profile is covered. The description's one genuine addition is 'Offline', which signals this queries a local catalog rather than live services — useful and not stated by the annotations alone. It does not mention pagination behavior (limit caps at 10, offset at 28) or the dependentRequired coupling of operation to domain, which are the behavioral wrinkles an agent would trip on.

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?

A single front-loaded sentence that names the tool's nature first ('Offline discovery') and then enumerates its capabilities. No filler and no repetition. It could earn a 5 only by trading a few words for the mode-to-parameter mapping that is currently missing.

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

Completeness2/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 values need no prose. But this is a five-parameter dispatcher whose parameters are undocumented in both schema and description, and whose conditional rule (operation requires domain) is invisible in the description. Given the tool's branching behavior, the definition is thinner than the surface it describes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description carries the full burden — and it names none of them. It never explains that 'query' is the search selector, 'domain' the browse selector, 'operation' the schema-retrieval selector, or what 'limit'/'offset' mean. It alludes to all three modes existing but leaves the mapping from parameter to mode entirely undisclosed.

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 identity: an offline discovery tool that does three things — browse domains, search operations, retrieve one operation's exact parameter schema plus example. The verb set and resource ('operations', 'domains') are concrete and distinguish it from the sibling domain tools (activity/health/profile/wellness), which appear to be the actual data endpoints. It stops short of 5 because the three modes are listed in one clause without being tied to any selector.

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?

The mode enumeration implies when each behavior applies (browse vs. search vs. fetch one schema), but the description never says which input selects which mode, and offers no explicit 'use this before calling the domain tools' routing advice. Usage is inferable from the brief rather than stated, which is the definition of a 3.

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