Skip to main content
Glama

Get my running paces

get_running_paces
Read-onlyIdempotent

How fast the athlete should run, from their own Goblin Gains records: with zone, the pace their steady runs held at that zone's heart rate first; then pace by HR zone from their steady runs, HR zones, critical speed and its source, the formula pace zones and training paces, the work and recovery bouts of recent interval runs, recent and planned runs, readiness. Needs the athlete's key.

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

Input Schema

NameRequiredDescriptionDefault
zoneNoThe HR zone of the run the athlete asks about, 1-5; omitted for all zones. Example: 2 for "a zone 2 run".
minutesNoHow long that run is. Example: 60 for "an hour".

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds a genuinely useful behavioral fact ('Needs the athlete's key') that annotations do not provide. However, the remaining substance is an enumeration of returned content that largely duplicates the output schema rather than disclosing new behavior.

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?

The list of return fields inflates the sentence into a run-on and displaces what matters most (what the tool is for and when to call it). It is not front-loaded: a clear opening is followed by a sprawling enumeration that should be left to the output schema.

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?

With only two optional parameters, full schema coverage, annotations, and an output schema, the definition is technically callable. But the description spends most of its length restating returns already documented elsewhere while omitting the guidance (when to pass zone/minutes) that would actually help an agent call it correctly.

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% and both parameters carry rich descriptions with examples, so the schema does the heavy lifting. The phrase 'with `zone`, the pace their steady runs held at that zone's heart rate first' hints that supplying zone shifts emphasis/ordering toward that zone's pace, which adds marginal meaning, but the 'minutes' parameter gets no added explanation at all.

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 opening clause ('How fast the athlete should run, from their own Goblin Gains records') conveys the resource and data source, but there is no explicit verb and the purpose is immediately buried under a long comma-separated enumeration of return fields (HR zones, critical speed, interval bouts, readiness). An agent can infer this returns pacing data, but the core purpose is muddied rather than sharpened.

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?

There is no statement of when to use this versus alternatives, no exclusions, and no context about when a caller would pass zone/minutes versus omit them beyond the schema's own examples. The only situational cue is that it requires the athlete's key, which is a prerequisite, not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources