TrackLab MCP Ultimate Edition

list_recent_activities

Retrieve recent training activities to review key metrics such as pace, heart rate, distance, and training load.

Instructions

Lists recent activities with pace, HR, distance, and training load.

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": "list_recent_activities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of activities to fetch (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation by using the verb 'Lists' and mentions return fields, but it does not clarify what 'recent' means, whether pagination exists, or the effect of the limit parameter. This is a minimal but acceptable level of transparency for a simple list operation.

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?

The description is a single sentence with no redundant words. All terms are meaningful and front-loaded, making it highly efficient and easy to parse.

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?

For a tool with one parameter and no output schema, the description is adequate but leaves gaps. It does not define the time window for 'recent,' mention the default behavior of the limit parameter, or describe the response structure. These gaps make it minimally viable but not fully complete.

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% with the 'limit' parameter fully documented in the input schema. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool lists recent activities and specifies the included metrics (pace, HR, distance, training load). It doesn't explicitly differentiate from sibling tool get_latest_activity, but the plural 'activities' implies a batch list rather than a single item, which provides some distinction.

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 is given on when to use this tool versus alternatives like get_latest_activity or training_dashboard. The description does not mention scenarios, prerequisites, or exclusions, leaving the agent without clear selection criteria.

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