Skip to main content
Glama

Workout details

get_workout
Read-only

One workout in full: every exercise and its sets (weight × reps, or seconds for timed holds). Get session_id from list_workouts.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe workout session id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 covered and need not be repeated. The description does add genuine behavioral value by disclosing the return shape (full exercise/set breakdown with weight×reps or timed seconds), which matters since there is no output schema. It stops short of mentioning ordering, pagination, or what happens for an invalid session_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, negligibly wasted, with the content of the result front-loaded and the id-provenance note last. Each sentence carries distinct information.

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 one-parameter read tool with annotations covering safety and no output schema, the description supplies both the return structure and how to obtain the required id. Nothing an agent needs in order to call it correctly 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 already 100%, so the field's format is documented structurally; the description adds the provenance hint that session_id comes from list_workouts, which the schema cannot express. That is meaningful value beyond the schema for a single-parameter tool.

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 a specific resource (one workout) and describes exactly what comes back: every exercise and its sets, with weight × reps or seconds for timed holds. The verb is only implied by the tool name rather than stated as 'retrieve a single session,' but the contrast with list_workouts is unmistakable.

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?

'Get session_id from list_workouts' tells the agent the prerequisite step and routes it to the correct sibling for id discovery. It does not state exclusions (e.g., don't use this for aggregate progress), but the guidance is clear about the intended call sequence.

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