Skip to main content
Glama

Nolio

Review a completed workout

review_training
Destructive

Coach only: mark a managed athlete's completed workout or race as viewed and, with comment, post a message the athlete is notified of on that workout.

id: the trn_… (workout) or cmp_… (race) handle from get_calendar(mode='real'). Show the athlete's name and the exact comment, and get the coach's go-ahead before posting: a sent message cannot be taken back here.

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": {
      "id": "<id>"
    },
    "name": "review_training"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
commentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses the parts an agent most needs: the call has an external side effect (the athlete is notified), the posted message is irreversible ('a sent message cannot be taken back here'), and authorization is restricted to coaches acting on managed athletes. This gives concrete meaning to destructiveHint=true and openWorldHint=false rather than just restating them.

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?

Front-loaded with the 'Coach only' gate, then the action, then per-parameter guidance in a compact two-block layout. The confirmation instruction and the irreversibility rationale are distinct and each earns its place; nothing is padding.

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 mutation with an outbound notification, the description covers authorization, id provenance, the confirmation step, and irreversibility, while an output schema already exists to describe return values. No gap remains that would cause a mis-call.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry both parameters, and it does: `id` is explained by handle prefix and source call, and `comment` is explained as the trigger for a notification-bearing message rather than a plain note. That is meaning an agent cannot get from the bare schema types.

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: mark a managed athlete's completed workout or race as viewed, and optionally post a comment. It also names the scope restriction ('Coach only') and the two id families (trn_… workouts vs cmp_… races), which separates it from read siblings like get_training and write siblings like update_planned_training.

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 clear preconditions and a workflow: it is coach-only, the id must come from get_calendar(mode='real'), and the coach must approve the exact comment before posting. It does not name an alternative for simply viewing a workout without commenting, but the when-to-use context is explicit rather than implied.

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