Skip to main content
Glama

challenge_state

Detect if the current page is blocked by a bot check, identify the challenge type, and report whether solve_challenge can clear it.

Instructions

Report whether the current page is behind a bot check. kind is "none" when the page itself is shown, else the kind of check ("cloudflare-interstitial", "turnstile-widget", "aws-waf" and others); solvable says whether solve_challenge can clear it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "challenge_state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.46

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it delivers the key behavior: the return semantics of `kind` (enumerating cloudflare-interstitial, turnstile-widget, aws-waf, plus a "none" baseline) and `solvable` as a boolean feasibility signal. It does not explicitly state that the call is read-only/non-mutating or that it requires an already-loaded page, leaving a small gap.

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?

A single front-loaded sentence with a parenthetical enumeration of kinds — dense and zero-waste. The embedded quoting of `kind`/`solvable` slightly crowds the sentence and the enumeration of check kinds is longer than strictly needed for selection.

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?

An output schema exists, so the description is not obligated to explain return values, yet it does briefly and usefully. For a no-parameter, read-only status probe, the only missing piece is an explicit statement of when in a workflow to call it (e.g. before or instead of solve_challenge on a failed read).

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?

Zero parameters, so the baseline is 4 and there is no parameter ambiguity to resolve. The prose instead spends its words on output field semantics, which is beyond what an empty parameter schema needs to convey.

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 object ("Report whether the current page is behind a bot check") and immediately separates itself from the closest sibling by naming solve_challenge as the actor that clears it. An agent can distinguish this diagnostic tool from solve_challenge, open, or snapshot without opening any schema.

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?

Usage context is clear: call it to learn if a bot check is present, and `solvable` tells you whether solve_challenge can clear it. It lacks an explicit trigger phrase (e.g. "call after navigation when a page looks blocked") and no when-not-to-use exclusion, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.