Skip to main content
Glama

Set a program ladder

set_program_ladder
DestructiveIdempotent

Adds or replaces the ladder for an exercise on the athlete's program. Progress on that exercise is kept (clamped to the new number of levels); a new ladder starts at level 0 today. Forks a preset first.

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>",
      "levels": "<levels>",
      "cleanSessionsToStepUp": "<cleanSessionsToStepUp>"
    },
    "name": "set_program_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsYes
exerciseIdYes
programNameNo
cleanSessionsToStepUpYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds genuine context beyond them: progress is preserved but clamped to the new level count, a new ladder starts at level 0 today, and it forks a preset first. That tells the agent what survives and what is lost, though it does not explain how excess-level progress is truncated or what re-running does to today's start date.

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?

Three tight sentences with the mutation semantics front-loaded and no filler. 'Forks a preset first' is terse to the point of ambiguity and costs some clarity, but nothing is wasted.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, nested-schema mutation with no output schema and zero parameter documentation, so the description carries a heavy burden and leaves major gaps: the levels array shape and the required cleanSessionsToStepUp are unexplained, as is the return/confirmation behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description explains none of them. The deeply nested 'levels' structure (names, prescriptions, methods, sets, rest) and the required 'cleanSessionsToStepUp' — a core tuning knob — receive no explanation at all, so the description does not compensate for the coverage gap.

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 states a specific verb pair and resource: 'Adds or replaces the ladder for an exercise on the athlete's program.' That clearly separates it from siblings like remove_program_ladder and set_ladder_level by implication, though it never names an alternative explicitly.

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?

'Adds or replaces' communicates the upsert nature and implies use when establishing or resetting a ladder, and 'Forks a preset first' hints at prerequisite state. There is no explicit when-to-use versus set_ladder_level or when-not guidance, so the agent must infer selection.

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