Skip to main content
Glama

create_challenge

Start a workout-days challenge for your clients (most days with a logged workout wins). Dates YYYY-MM-DD, end on/after start and not in the past; the server caps length and how many run at once. forWholeGym: gym owners only — includes every gym member. (confirm-gated: previews until confirm: true)

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": {
      "input": "<input>"
    },
    "name": "create_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description adds meaningfully more — that calls are confirm-gated and return a preview until confirm: true, and that the server enforces caps on challenge length and concurrent active challenges. It still omits what the preview payload contains and what happens on validation failure, so a 5 isn't warranted.

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?

Front-loaded with purpose, then constraints, then the parameter caveats, then the confirm gate — a logical order with no filler. The telegraphic parenthetical phrasing ('forWholeGym: gym owners only — includes every gym member') is compact but slightly terse for a reader parsing it cold.

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 nested, confirm-gated mutation with no output schema, the description covers the constraints an agent must satisfy before calling and how execution is gated. What's genuinely missing is post-call behavior — whether the preview echoes the payload and how failures are reported — which is a modest gap rather than a blocking one.

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?

With only 50% schema coverage and a nested input object, the description compensates well: it explains the date format and cross-field rule (end on/after start, not in the past), the permission meaning of forWholeGym, and the operational meaning of confirm. title and description fields are left to the schema, which is acceptable since they are 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?

States a specific verb+resource ('Start a workout-days challenge for your clients') and even defines the win condition (most logged workout days), which makes the resource concrete. It never names or contrasts a sibling such as set_challenge_active or delete_challenge, so it stops just short of the top band.

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 real preconditions: dates in YYYY-MM-DD, end on/after start, not in the past, and forWholeGym restricted to gym owners. It does not say when to prefer this over the sibling challenge tools (e.g., use set_challenge_active to re-enable an existing one), so the alternative-selection guidance is implicit rather than explicit.

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.