Skip to main content
Glama

get_workout_plan

Read-only

Full detail of one client workout plan: every exercise (sets, reps, repsMin when reps is a range like 8-10, rest, section, supersetGroup, notes, cardio fields) and the original PDF's text when the plan came from a coach's PDF. Pass the plan _id from list_workout_plans. If document is present with no exercises/meals, the plan IS the coach's PDF (shared as-is): document.text is what the PDF says. A null document.text means the PDF is scanned or unreadable — tell the coach to open the plan on the web and use "Turn into a trackable plan" so it can be read and edited.

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": {
      "planId": "<planId>"
    },
    "name": "get_workout_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value beyond them: it explains the PDF-backed plan case, that `document` with no exercises/meals means the plan IS the coach's PDF, and that a null document.text indicates a scanned/unreadable PDF. It does not cover error behavior for an invalid or foreign planId, which keeps it below 5.

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?

Front-loaded with the primary payload description, then the id source, then the PDF edge cases in priority order; the field enumeration is dense but each item is load-bearing for an agent reading the result. The long parenthetical field list and the quotation marks around 'Turn into a trackable plan' add a little bulk but no dead sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of explaining return values and does so thoroughly, including the degenerate PDF/scanned-document cases an agent would otherwise misreport to a coach. Nothing essential to invoking or interpreting this single-parameter read tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema only says planId is a non-empty string — so the description must compensate, and it does by identifying the value as the plan _id obtained from list_workout_plans. It adds no format example or mention that template ids are not valid, which would have pushed it higher.

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?

States a specific verb and resource ('Full detail of one client workout plan') plus exactly what the payload contains — exercises with sets/reps/rest/supersetGroup and PDF-sourced text. It is clearly distinguished from list_workout_plans (which supplies the id) and from template tools by the 'one client workout plan' framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where the required argument comes from ('Pass the plan _id from list_workout_plans') and gives a concrete recovery path when document.text is null ('tell the coach to open the plan on the web and use Turn into a trackable plan'). It does not state when to prefer get_workout_plan_template instead, so the alternative-selection guidance is incomplete.

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.