Skip to main content
Glama

Training plan

get_training_plan
Read-only

What's planned: the active split and its days, and planned workouts for the coming days (with any missed days that were made up).

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

Input Schema

NameRequiredDescriptionDefault
days_aheadNoDefault 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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=false, so the safety profile is fully covered and the description is not required to restate it. What the description does add is return-content semantics: it will include the active split with its days and planned workouts, and it explicitly notes that missed days which were made up are surfaced — a non-obvious inclusion rule worth calling out. It stops short of saying how days_ahead scopes the result or what the plan looks like when no split is active.

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?

One front-loaded sentence with no filler; the 'What's planned:' lead immediately frames the payload. It is slightly tangled by the repeated 'and' clause and the parenthetical, but nothing is wasted and nothing extraneous is included.

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?

With no output schema, the description must carry return-value meaning, and it does so competently by enumerating split, days, and planned workouts plus the made-up-missed-day rule. For a one-optional-parameter read tool with full annotation coverage, the remaining gap — the boundary against get_training_overview — is modest rather than disqualifying.

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% for the single optional parameter, including its default of 7 and its 1–28 bounds, so the schema carries the parameter burden. The description adds no interpretation of days_ahead (e.g., whether it governs only planned workouts or the split display too), which leaves it at the baseline for high-coverage schemas.

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 names the specific resource content: the active split, its days, and planned workouts for the coming days, including made-up missed days. That is concrete and distinguishable in substance from a generic workout logger, but it never explicitly contrasts with the closely named sibling get_training_overview or list_workouts, so an agent must infer the boundary.

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 or when-not-to-use guidance and no named alternative. In a sibling set containing get_training_overview and list_workouts, the agent gets no explicit signal for choosing this planning view over an overview or a workout listing; usage is only weakly implied by the phrase 'What's planned'.

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