Skip to main content
Glama

activity

Read-onlyIdempotent

Search, retrieve, and download Garmin Connect fitness records, including workout types, details, summaries, and workout data, for personal health queries.

Instructions

Activity search, details, types, workouts, downloads and activity summaries. Use discover for exact operation parameters.

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": {
      "operation": "<operation>",
      "parameters": "<parameters>"
    },
    "name": "activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYes
parametersYesExact operation arguments. Use discover(domain, operation) for the schema.

Output Schema

NameRequiredDescriptionDefault
dataYes
errorNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds essentially nothing beyond the discover pointer: it does not say what download_activity returns (a file, a URL, inline content), whether results are paginated or date-bounded, or how wellness_activity_range differs from search_activities.

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 sentences with no filler, and the discover instruction is placed after the scope statement where it is easiest to act on. The first sentence is a bare noun pile, which costs a little readability but nothing is wasted.

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?

This is a complex six-operation dispatcher with a nested required parameters object, and the description covers the discover dependency needed to call it at all; an output schema exists so return values needn't be explained. It is still incomplete on routing versus the health/wellness siblings and on per-operation behavioral differences such as download semantics.

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?

The schema documents the operation enum but the nested 'parameters' object is deferred with 'Use discover(domain, operation) for the schema,' and the description repeats that same deferral rather than adding meaning. The topical words in the description do give a loose mapping to individual operation names, which is mild added value, but with only 50% schema coverage the description does not close the gap itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun list ('Activity search, details, types, workouts, downloads and activity summaries') rather than a verb+resource statement, so an agent must infer that this is a single dispatch tool fronting six activity operations. The enumerated topics do map roughly onto the operation enum, which helps, but nothing distinguishes this tool from the sibling 'health' or 'wellness' tools that likely expose overlapping data.

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 only procedural guidance is 'Use discover for exact operation parameters,' which correctly establishes the two-step discover-then-call workflow. There is no guidance on when to pick this tool over 'health', 'profile', or 'wellness', and no statement of exclusions, so the usage boundary is implied by topic 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