Skip to main content
Glama

adapt_exercise

Adapt a practice you describe for your team: fewer players, a younger age group, a smaller space. Returns the adapted practice with setup, rules, coaching points and progressions

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>"
    },
    "name": "adapt_exercise"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeNoWhat to change, for example "only 8 players", "for under 8s" or "half the space"
exerciseYesDescribe the practice to adapt (setup, rules, players)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no output schema, the description earns credit for disclosing the return payload: setup, rules, coaching points and progressions. Annotations already cover the safety profile (destructiveHint=false, openWorldHint=false). It does not clarify whether the adaptation is persisted anywhere, which is a minor gap given readOnlyHint=false.

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 tight sentences: the action and its dimensions come first, then the return contents. Every clause carries information an agent can act on, with no filler.

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 two-parameter generation tool with no output schema, the description covers both the input intent and the shape of the result, which is what an agent needs to invoke it. Only the persistence/state question is left unaddressed.

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 both parameters are already documented. The description's examples (fewer players, younger age group, smaller space) largely restate the `change` parameter's own examples, adding little new semantic detail. Baseline 3 applies where the schema does the heavy lifting.

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 (adapt) and a specific resource (a practice the caller describes), plus the adaptation dimensions (player count, age group, space). This clearly separates it from siblings like search_drills (find existing drills) and generate_session_plan (build an entire session).

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?

The phrase 'a practice you describe' tells the agent the input is a caller-supplied practice rather than a library drill, which implicitly routes away from search_drills. It does not name an explicit alternative or state when not to use it, so it falls short of full when/when-not guidance.

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