coros-training-mcp

Overview Schema Source Related Servers Discussions Admin

Get Activity Detail

get_activity_detail

Retrieve detailed information for a single Coros activity using its ID and sport type. This enables review of workout data and performance metrics.

Instructions

Fetch full detail for a single Coros activity.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_detail"
  }
}

Input Schema

Name	Required	Description	Default
`sport_type`	No	Sport type ID from list_activities (e.g. 200=Road Bike, 201=Indoor Cycling, 100=Running). Required for the API call to succeed.
`activity_id`	Yes	The activity ID (labelId) from list_activities.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden and delivers almost nothing: no statement that this is a read-only call, no auth/permission context, no error behavior. It also omits the notable quirk that sport_type is effectively required for the API call to succeed, which the schema flags but the description ignores.

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 front-loaded sentence with no filler. Every word earns its place and the core action is immediately visible.

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?

An output schema exists, so return values needn't be explained, and the schema covers both parameters. However, for a tool with zero annotations the description should at least signal that it is a read operation and how it relates to list_activities; that gap leaves it only minimally adequate.

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?

Schema description coverage is 100%, so both activity_id and sport_type are already documented with source hints (labelId, list_activities) and example enum values. The description adds nothing beyond that, which is the baseline expectation when the schema does the work.

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 verb (fetch) and resource (full detail for a single Coros activity), making it clearly distinct from list_activities and export_activity_file. It stops short of explicitly naming which sibling to use first, but the single-vs-list contrast is inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no named alternatives. The agent must infer that activity_id comes from list_activities and that this tool is the follow-up drill-down step; nothing in the description says so.

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