Skip to main content
Glama

Report a workout

report_workout

A user's verdict on a workout from these tools: a mistake (wrong equipment, a weight, a dose that cannot fit), or a workout they found bad or good. Stores the user's words for Goblin Gains, nothing else about the user.

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": {
      "note": "<note>",
      "verdict": "<verdict>"
    },
    "name": "report_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesWhat the user said about the workout, in their words. Example: "Farmers carry needs two dumbbells; I said I have one."
verdictYesOne of mistake, bad, good: "mistake" (something in it is wrong), "bad" (it works but is a poor workout), "good". Example: "mistake".
workoutNoThe workout's save link from generate_workouts, or its id; omitted for the tools as a whole. Example: "https://app.goblingains.com/w/<id>".

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / workout / description
      Previous value: -"The workout's save link from suggest_workouts, vary_workout or generate_workouts, or its id; omitted for the tools as a whole. Example: \"https://app.goblingains.com/w/<id>\"."New value: +"The workout's save link from generate_workouts, or its id; omitted for the tools as a whole. Example: \"https://app.goblingains.com/w/<id>\"."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a write operation (readOnlyHint false, idempotentHint false, destructiveHint false). The description adds useful context beyond that: it stores the user's words for Goblin Gains and 'nothing else about the user,' which clarifies data retention and privacy scope. It does not contradict annotations.

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?

It is short and front-loads the core purpose and verdict categories. The phrasing around 'a dose that cannot fit' is domain-specific but understandable, and no major sentence is wasted.

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?

Given an output schema exists, the description need not explain return values. It covers the write scope, data retention, and verdict meanings; only explicit sibling routing or auth expectations are missing, which are minor for this tool.

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 100%, so the schema already documents the note, verdict, and workout parameters. The description restates the verdict categories but adds little syntax or meaning beyond the schema; baseline 3 is appropriate.

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 and resource: it records a user's verdict on a workout, enumerating the three verdict meanings (mistake, bad, good). It is clear enough to distinguish from generation or listing siblings, though it does not name those siblings 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?

It explains the verdict distinctions (mistake = something is wrong, bad = works but poor, good) and notes the 'tools as a whole' case via the schema. It does not explicitly state when to choose report_workout versus other tools, but the usage context is strongly 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