Exercise Images

Show a workout

show_workout

Read-onlyIdempotent

Shows a training session, or a programme of several, as one card: each exercise with its drawing and what was prescribed, opening to its details when tapped. Exercises are named in English, in the call and on the card, and matched to the library's names, with word order, plurals, abbreviations and small misspellings understood; one that matches nothing is shown by its name with the closest exercises. Every field but an exercise's name is optional, so a plain list of exercises is a workout too. Returns the workout as text with each drawing's URL, and the exercises as JSON with their data and image URLs.

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": {
      "sessions": "<sessions>"
    },
    "name": "show_workout"
  }
}

Input Schema

Name	Required	Description
`aim`	No	What the workout is for.
`lang`	No	The language of the card's own words, such as headings, rounds and rest: en or sv, English for any other. Exercise names stay English.
`title`	No	The title on top.
`sessions`	Yes	One session, or a programme's sessions in order.
`duration_min`	No	The length in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds substantial context beyond that: card rendering with drawings, tap-to-open details, English exercise-name matching with tolerance for word order, plurals, abbreviations and misspellings, fallback to closest exercises for unmatched names, and the exact return shape including text and JSON with URLs.

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 a dense but front-loaded paragraph: purpose first, then behavioral details, then return format. Every sentence contributes, though the exercise-name matching clause is long and slightly run-on.

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?

For a complex nested workout schema with no output schema, the description covers rendering, name matching, optionality, and return values sufficiently for an agent to invoke the tool correctly. The schema itself handles granular field descriptions.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that exercise names are matched to the library with normalization and that all fields except the exercise name are optional. It does not explain every parameter, but the important semantic behavior of the 'move' field is covered.

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?

States a specific verb ('Shows') and resource ('training session, or a programme of several') and describes the card rendering, so the agent knows this presents a workout rather than searching exercises. It does not explicitly name or distinguish itself from the sibling exercise-finding tools, but the purpose is clear.

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

Usage Guidelines3/5

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

Provides some usage context by saying every field except an exercise's name is optional, so a plain list of exercises is valid. However, it gives no explicit when-to-use guidance versus alternatives like find_exercise or list_exercises, and no exclusions.

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

All Exercise Images tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?