Skip to main content
Glama

get_training_readiness

Read-only

Returns your training readiness score and the factors behind it for a given date, so you can decide whether to push harder or recover. Use it to plan training based on Garmin metrics.

Instructions

Get training readiness data with curated metrics

    Returns training readiness score and contributing factors.

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_training_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by stating what is returned (a score plus contributing factors), which matters because there is no output schema. It says nothing about data availability, latency, or what happens for dates without recorded data.

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 description is short and front-loads the purpose before the argument details, which is the right order. 'With curated metrics' is vague filler that does not add information, and the Args block restates a single documented parameter, though both are minor.

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?

For a single-parameter read-only getter with no output schema, the description covers purpose, the shape of the return value, and the parameter format, which is roughly what an agent needs to invoke it correctly. The missing piece is any hint about how this differs from the morning-readiness sibling or what an empty result looks like.

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 0% and the only parameter is described merely as a string titled 'Date', so the description carries the burden and does specify the required YYYY-MM-DD format, which is genuine added value. It does not clarify the timezone or whether the date refers to the readiness measurement day, leaving interpretation partly open.

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 gives a specific verb and resource ('Get training readiness data') and states the return contents ('training readiness score and contributing factors'). It stops short of distinguishing this from the closely named sibling get_morning_training_readiness, so an agent cannot tell from the text why it would pick one over the other.

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 when-to-use guidance, no prerequisites, and no statement of when this tool is the wrong choice. The only usage hint is the required date argument, which the schema already imposes. For a family with many similarly named training tools, the omission of routing guidance is a real gap.

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