Skip to main content
Glama

mark_workout_completed

Mark a workout as done when the user did it without a recording; completed=false reverts a manual mark.

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": {
      "workout_id": "<workout_id>"
    },
    "name": "mark_workout_completed"
  }
}

Input Schema

NameRequiredDescriptionDefault
completedNo
workout_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / completed
      Added value: +{
      +  "default": true,
      +  "title": "Completed",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds genuine behavioral context by stating the operation is reversible via completed=false and applies only to manual marks rather than recorded activities. It does not discuss downstream effects such as streaks or statistics, which keeps it short of a 5.

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?

A single sentence that front-loads the primary action, then adds the scoping condition and the reversal mechanism in a compact clause. Every element earns its place with no filler.

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 simple two-parameter mutation with an output schema and annotations covering safety, the description supplies what structured data cannot: the manual-only scope and the undo path. Minor gaps remain around idempotency and side effects on derived metrics, but nothing needed to call it correctly is missing.

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 description coverage is 0%, so the description must carry parameter meaning, and it clarifies the non-obvious `completed` flag by defining the revert semantics of false rather than merely restating the boolean. `workout_id` is left implicit, but its name and uuid format make its role self-evident.

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 pairs a specific verb ('mark ... as done') with a specific resource ('a workout') and scopes it to workouts the user did without a recording, so the intent is unambiguous. It does not explicitly contrast with siblings like delete_workout, but the action is distinct enough that confusion is unlikely.

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?

It gives a clear use condition ('when the user did it without a recording') and an explicit inverse operation ('completed=false reverts a manual mark'), which doubles as guidance for correcting mistakes. No alternative tool is named, but the stated condition is strong enough to guide selection.

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