Skip to main content
Glama

Set a program rule

set_program_rule
DestructiveIdempotent

Adds or replaces a rule that belongs to this program (it doesn't follow the athlete to another program). Rules about the athlete (e.g. their tennis) are set with set_athlete_rule. Forks a preset first. The app shows the rule to the athlete and does not apply it. check is still required and is stored, but nothing reads it.

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": {
      "rule": "<rule>"
    },
    "name": "set_program_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYes
programNameNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the fork-a-preset side effect, that the rule is surfaced to the athlete but never enforced by the app, and that `check` is required and persisted yet unread. These are exactly the facts an agent cannot infer from readOnly/destructive/idempotent hints, and they are consistent with destructiveHint=true and idempotentHint=true ('adds or replaces').

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?

Five short sentences, each carrying a distinct decision-relevant fact, with the scope and the sibling alternative front-loaded. No filler or restatement of the name.

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 destructive mutation with a deeply nested, four-branch schema and no output schema, the description covers scope, side effects, and the non-enforcement caveat well. The remaining gap is that the rule variants themselves are left entirely to the schema, which has no field-level descriptions.

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 0% and the nested `check` object has four polymorphic variants, but the description only illuminates one field (`check` is required and stored but unused). It says nothing about the variant semantics (no_block_before_event, limit_block_during_event, stop_exercise_on_pain, etc.) or about programName, so compensation is partial.

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 ('Adds or replaces a rule that belongs to this program') plus an explicit negative scope ('it doesn't follow the athlete to another program'). It also names the sibling that handles the adjacent case (set_athlete_rule), so an agent can separate the two without opening either schema.

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 a clear routing rule: athlete-level rules go to set_athlete_rule, program-level rules go here. It also implies this is the write counterpart to remove_program_rule. It stops short of saying when a rule should be replaced vs. added as new, but the alternative is named explicitly.

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