Skip to main content
Glama
smart-gym-mcp
by sla1k

smartgym_get_routine

Read-only

Retrieve a SmartGym routine split into warmup, main, and cooldown sections with exercise IDs, planned sets, rest notes, and recent session history for review or edits.

Instructions

Get a routine split into warmup, main and cooldown sections.

Each exercise shows its exercise_id (what the edit tools take), rest, note, planned
template sets, and up to `history_depth` recent sessions (reps + weight_kg) with the
latest session's top set and total volume.

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": {
      "routine": "<routine>"
    },
    "name": "smartgym_get_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
routineYes
history_depthNo

Output Schema

NameRequiredDescriptionDefault
daysYes
goalYes
mainYes
nameYes
noteYes
warmupYes
archivedYes
cooldownYes
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral detail -- what each exercise block contains and that history is capped at history_depth -- but says nothing about missing routines, errors, or pagination behavior.

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?

Two short sentences, front-loaded with the section split before the per-exercise detail. No filler; the second sentence is a dense list rather than prose bloat.

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 read-only two-parameter tool this is close to complete: it covers the return shape and the history-depth effect. The remaining gap is the ambiguity of the `routine` identifier, which neither schema nor description resolves; the described return values are partly redundant given an output schema exists.

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 0%, so the description must carry parameter meaning. It explains history_depth well ("up to history_depth recent sessions") and what the returned exercise_id is for, though it never clarifies what the required `routine` argument accepts (ID vs. name).

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?

Description states a specific verb and resource ("Get a routine") and even defines the output structure (warmup, main, cooldown), which separates it from list-oriented siblings like smartgym_list_routines. It does not name any sibling explicitly, so the differentiation is implied rather than stated.

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?

No explicit when-to-use/when-not-to-use statement or named alternative. The parenthetical "exercise_id (what the edit tools take)" implies this is the read step preceding edit tools, but the agent must infer that workflow itself.

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