Skip to main content
Glama

set_challenge_active

Pause (hide from clients) or re-enable a challenge. (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>",
      "isActive": "<isActive>"
    },
    "name": "set_challenge_active"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only give a generic safety profile (readOnlyHint=false, destructiveHint=false), so the description carries real weight here and delivers: it discloses the client-visible effect ('hide from clients') and the two-step confirm-gated preview behavior that otherwise could only be discovered by reading the schema. It does not state whether pausing is reversible in terms of lost data or what happens to an in-progress challenge's progress.

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?

Two compact sentences, front-loaded with the action and effect, with the confirm-gate detail parenthetically scoped. Nothing is padded, though the parenthetical is slightly cryptic in isolation.

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 three-parameter state setter with no output schema, the description covers action, client-visible effect, and the confirm mechanics, which is most of what an agent needs. The remaining gap is the id parameter and any hint about the returned preview payload.

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 33%; confirm is fully documented in the schema, but id and isActive are bare. The description implies the isActive mapping (pause vs re-enable) without stating it explicitly, and says nothing about what id identifies or its format. Baseline 3 is appropriate since it adds partial meaning but leaves the undocumented id parameter untouched.

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 pair and resource: 'Pause (hide from clients) or re-enable a challenge', which makes the state toggle and its client-visible effect unambiguous. It does not name or contrast with sibling setters like set_coupon_active or delete_challenge, so it stops short of full sibling differentiation.

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?

The two modes of use (pause vs re-enable) are clear from the description, and the confirm-gate note tells the agent that a preview is the default path. There is no explicit guidance on when to prefer delete_challenge over pausing, nor any stated prerequisites such as the challenge needing to exist.

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.