Skip to main content
Glama

Set one of the athlete's own rules

set_athlete_rule
DestructiveIdempotent

Adds or replaces one of the athlete's OWN rules, which apply on every program (e.g. no strength the day before a match). Never changes the program. 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_athlete_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (destructive=true, idempotent=true), the description discloses the crucial non-obvious behavior: the app displays the rule to the athlete but does not enforce it, and the required `check` field is stored but read by nothing. That resolves why a destructive replace is low-risk. It does not say what happens to an existing rule with the same id beyond 'replaces', which is a minor remaining gap.

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 short sentences, front-loaded with the core action and scope, then the example, then the two most surprising behaviors. No filler and nothing repeated from the schema.

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 single nested-object parameter with a four-way oneOf and no output schema, the description covers the semantics an agent most needs: it is additive/replacing, program-independent, and not enforced. The missing piece is a mapping of the check variants and the role of `id` in replacement.

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%, so the description carries the burden, and it clarifies only `check` (required, stored, unread). It says nothing about `id` being the replacement key, `text` limits, or what the four oneOf check variants mean, leaving most of a complex nested schema unexplained.

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 gives a specific verb pair ('adds or replaces') and a precise resource ('one of the athlete's OWN rules, which apply on every program'), with a concrete example of a rule. 'Never changes the program' implicitly separates it from program-level siblings like set_program_rule, though no sibling is named outright.

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: athlete-wide rules that hold across every program, versus something that would 'change the program'. There is no explicit when-not or named alternative such as set_program_rule, so an agent must infer the routing decision.

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