Skip to main content
Glama

swap_exercise

Read-only

Exercise substitution from a personal trainer's exercise library (MTFIT): get 1 to 3 alternatives for one exercise because of no equipment (gym, home dumbbells, bands or bodyweight), pain (shoulder, lower back), too hard, or variety. Each with a coaching cue. Text plus structured JSON. Not medical advice.

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": {
      "exercise": "<exercise>",
      "reason": "<reason>"
    },
    "name": "swap_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
muscleNoThe muscle it trains. Needed only if the exercise is not in the MTFIT library.
reasonYesWhy it needs replacing.
exerciseYesThe exercise to replace, e.g. 'Barbell deadlift' or 'Cable fly'.
equipmentNoEquipment available now. Defaults to the exercise's own setting.
pain_areaNoWhere it hurts, when reason is pain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and closed-world scope, so the description only needs to add context, which it does: a bounded result size (1-3 alternatives), a per-item coaching cue, a text+JSON response shape, and a 'not medical advice' disclaimer relevant to the pain path. It does not say what happens when the exercise is outside the library.

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?

Compact and front-loaded with the core operation, followed by reasons, output shape, and a disclaimer — every clause carries information. The parenthetical equipment list is slightly noisy but not wasteful.

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

Completeness3/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 burden of explaining returns and does so at a high level (1-3 alternatives, coaching cue, text plus JSON), which is helpful. It leaves open the behavior when the exercise is missing from the library and how the optional muscle/equipment defaults interact, so it is adequate but not complete.

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%, so the parameters are already documented; the description only echoes the equipment and pain-area dimensions without adding format or interaction rules. Baseline 3 is appropriate.

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+resource: substitute one exercise from an MTFIT personal-trainer library, returning 1-3 alternatives each with a coaching cue. It does not name or contrast with any sibling, but the described operation is distinct enough from build_program/adjust_program to be unambiguous.

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?

Enumerates concrete trigger conditions — no equipment (gym, home dumbbells, bands, bodyweight), pain (shoulder, lower back), too hard, or variety — which maps directly onto the reason enum. No explicit exclusions or 'use X instead' routing, so it falls short of a 5.

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