Skip to main content
Glama

Update program details and pain tracking

set_program_info
DestructiveIdempotent

Changes the athlete's program details: name, coachBrief, equipmentNote, trackingAreas (the body areas the app asks about after a session) and trackPainDefault (whether it asks about pain). Only the fields given change; the rest stay as they are. At least one field is required.

  • On a preset (Strong Back, Strong Knees) this first saves the athlete's own custom copy and moves them onto it: under name if given (a name already taken gets a number, e.g. "Tennis season 2"), else " (custom)".

  • The empty "Build with your coach" program has no days: this tool is refused until a day is added with set_program_day.

  • trackPainDefault is the program's default; the athlete's own pain-tracking setting still wins.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_program_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe program's name. On a preset, the name of the athlete's custom copy.
coachBriefNoWhat the program is for and its coaching context.
equipmentNoteNoThe equipment the program needs or the athlete has.
trackingAreasNo1–4 body areas, no repeats, that the app asks the athlete to rate 0–10 after a session.
trackPainDefaultNoWhether the app asks about pain after a session. The athlete's own setting wins.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-update semantics (only supplied fields change), preset forking into a custom copy with deterministic naming and collision numbering, the refusal condition on dayless programs, and precedence between trackPainDefault and the athlete's own setting. This is exactly the kind of context annotations cannot express.

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?

Front-loads the field list and the partial-update guarantee, then uses bullets for the three conditional behaviors so each earns its place. Slightly dense, but no sentence is redundant.

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?

Covers mutation, partiality, preset forking and refusal conditions for a tool with no output schema. It never says what the call returns (e.g. the updated or newly forked program), which is the one remaining gap for a write tool whose destructiveHint is true.

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 coverage is 100%, so the baseline is 3; the description adds real meaning on top by explaining that name renames the forked custom copy on a preset, that a taken name gets a numeric suffix, and that trackPainDefault is only a default overridden by the athlete's setting.

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 and resource (changes the athlete's program details) and enumerates the exact fields touched, distinguishing it from siblings like set_program_day, set_program_goal and update_profile that also mutate program state.

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?

Gives concrete preconditions and routing: at least one field is required, and on an empty 'Build with your coach' program the call is refused until a day is added with set_program_day. It does not state when to prefer a sibling for non-matching fields, but the scoping is otherwise clear.

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