Running Companion MCP Server

This server has been deprecated

Personal project, not offered for public use.

Activity details

get_activity

Read-only

Retrieve detailed data for a Garmin running activity, including summary, dynamics, zones, planned versus actual steps, laps, and best efforts; defaults to the latest run.

Instructions

Everything about one activity: summary, running dynamics, zones, the planned workout steps, planned vs actual per step (executed_steps: auto-laps merged back into steps, pace judged against the target as on/fast/slow), every lap and best efforts. Defaults to the latest activity.

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

Input Schema

Name	Required	Description	Default
`activity_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Nov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: the tool falls back to the latest activity when no ID is supplied, and it explains the executed_steps processing (auto-laps merged back into steps, pace judged on/fast/slow), which the agent could not infer from structured fields.

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 dense sentence that front-loads the resource and then enumerates the payload; the parenthetical on executed_steps earns its length because it explains derived semantics. No filler or repetition.

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, the description usefully enumerates returned sections, and the single optional parameter is accounted for. It stops short of covering edge cases such as an unknown activity_id or out-of-range values, which would matter for correct invocation.

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?

Schema description coverage is 0% for the single activity_id parameter, so the description must carry the load. It does so by disclosing the default-to-latest behavior, which conveys that the parameter is optional and what omission means — details absent from the schema, which declares no default.

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 a specific resource (one activity) and enumerates its contents — summary, running dynamics, zones, planned vs actual steps, laps, best efforts — so an agent knows exactly what payload to expect. It lacks explicit sibling differentiation, since best efforts are also exposed by get_best_efforts and no mention is made of list_activities for discovering IDs.

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 implied: call this for detail on a single activity, and the 'defaults to the latest activity' clause tells the agent it can be invoked with no arguments. There is no explicit when-not guidance or pointer to alternatives such as list_activities or get_best_efforts.

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

Deploy Server