Skip to main content
Glama
Sign In
Coros MCP Server

Coros MCP Server

by Dhivakarkd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_activity_details

Retrieve detailed activity metrics, laps, time-series data, training zones, and weather information for a specific activity using its label ID and sport type.

Instructions

Get comprehensive activity data including summary metrics, laps, time-series data, zones, and weather

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": {
      "labelId": "<labelId>",
      "sportType": "<sportType>"
    },
    "name": "get_activity_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdYesThe activity label ID
sportTypeYesThe sport type number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only lists data types included (summary metrics, laps, etc.). No disclosure of side effects, authentication needs, rate limits, or return format.

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?

Single sentence, 12 words, no waste. Front-loaded with key verb and resource. Achieves high density of information with zero filler.

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?

For a tool with no output schema and no annotations, the description is incomplete. It does not mention pagination, limits, or response structure, despite likely returning a complex object.

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 coverage is 100%, so parameters are already described. Description adds no meaning beyond schema; it only lists outputs. Baseline 3 is appropriate.

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

Purpose5/5

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

Description clearly states the action 'Get' and the resource 'comprehensive activity data', listing specific data types. This distinguishes it from siblings like get_recent_activities (list) and get_activity_file_url (file download).

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 guidance on when to use this tool versus alternatives. Does not mention that it is for a single activity, while get_recent_activities lists all. Lacks any when-to-use or when-not-to-use context.

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