Skip to main content
Glama

delete_challenge

Destructive

Permanently delete a challenge and its leaderboard. Prefer set_challenge_active false to just hide it. (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": {
      "id": "<id>"
    },
    "name": "delete_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is context, and it delivers: permanence, the cascading loss of the leaderboard, and confirm-gating that only previews until confirm:true. It stops short of saying what else is affected (entries, historical data) or what permissions are required, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses with the destructive scope front-loaded, followed by the safer alternative and the confirm mechanic. Tight and well ordered; the parenthetical gating note is slightly redundant with the `confirm` schema description but harmless.

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 destructive, confirm-gated mutation with no output schema, the description covers what is destroyed, that it is irreversible, the safer alternative, and the two-step confirm flow. Remaining gap is the undocumented `id` parameter and what the preview response actually contains.

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 coverage is 50%: `confirm` is fully documented in the schema, while `id` has no description anywhere. The description reinforces the confirm gate but adds nothing about what `id` accepts or how to obtain it, so it only partially compensates for the coverage gap.

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 ("Permanently delete a challenge and its leaderboard") plus the cascade scope, which distinguishes it from the sibling set_challenge_active. An agent knows exactly what this destroys without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the alternative: "Prefer set_challenge_active false to just hide it," naming the sibling and the condition (hide vs. permanently remove) that selects it. This is the exact when-to-use/when-not guidance the dimension asks for.

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.