Skip to main content
Glama

Move a ladder level

set_ladder_level
DestructiveIdempotent

Moves one ladder of the athlete's current program up or down by one level (to is the 0-based level index, as in get_athlete_context). The server does not gate the move; cleanCount and cleanNeeded are returned. reason (short) is kept in the audit log. The server then re-checks planned coach sessions from today at the new level: revalidated lists days it updated and withdrawn days that no longer pass.

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": {
      "exerciseId": "<exerciseId>",
      "to": "<to>",
      "reason": "<reason>"
    },
    "name": "set_ladder_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
reasonYes
exerciseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description goes well beyond them: it discloses that no server-side validation gates the move, that cleanCount/cleanNeeded are returned as the caller's check, that `reason` lands in an audit log, and — critically — that planned coach sessions are revalidated with `withdrawn` days silently losing their sessions. That is exactly the destructive side effect an agent needs before invoking.

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?

Four tight sentences, front-loaded with the action, then the indexing convention, then the write/audit behavior, then the downstream effects. No filler sentences; each clause carries information the agent could not get from the schema or annotations.

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 destructive, output-schema-less mutation with three undocumented parameters, the definition covers what is required: index semantics, the absence of server gating, the returned counters, the audit trail, and the revalidation side effects with their two result lists. An agent can call this correctly and anticipate consequences.

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?

With 0% schema coverage the description must carry the parameter burden, and it explains `to` as a 0-based level index tied to get_athlete_context and `reason` as a short audit-log string matching the minLength constraint. `exerciseId` is left implicit, relying on 'one ladder of the athlete's current program' and a self-describing 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?

The opening sentence names a specific verb and resource ('Moves one ladder of the athlete's current program up or down by one level'), which is enough to separate it from structural siblings like set_program_ladder or remove_program_ladder. The only blemish is a mild internal tension: 'up or down by one level' suggests a ±1 nudge, while the schema's `to` accepts any 0-based index.

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?

Usage is implied rather than stated: the description points to get_athlete_context for the level index convention and warns that 'The server does not gate the move', which tells the agent it must verify eligibility itself. There is no explicit when-to-use/when-not or a named alternative for restructuring a ladder versus moving a level.

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