Skip to main content
Glama

solve_challenge

Solve Cloudflare challenges on the current page by handling 'Just a moment...' pages and Turnstile widgets, pressing the checkbox when shown. Use when auto-solve is off or a challenge appears later.

Instructions

Solve the Cloudflare challenge on the current page: the "Just a moment..." page or a Turnstile widget, pressing its checkbox if it shows one. Only needed when open ran with auto-solve off or a widget appeared later. Returns status, solved, remaining, title and url.

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": "solve_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_secondsNoHow long to wait for the challenge to clear, in seconds.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.47-alpha
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"How long to wait for the challenge to clear, in seconds."
  2. First observedv0.1.46

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully says the tool presses a checkbox if one appears and lists return fields, but it does not describe failure behavior, timeout handling beyond the schema, or side effects of interacting with the page.

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?

Two sentences, front-loaded with the core action and followed by the usage condition and return fields. There is no redundant or wasted wording.

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?

The description covers the action, when to use it, the checkbox behavior, and the return fields. Since an output schema exists, listing return values is extra rather than required, but the definition is nearly complete for a one-parameter browser-automation tool.

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?

There is one parameter, `timeout_seconds`, and schema coverage is 100%, so the schema already fully documents its meaning. The description does not add parameter-specific detail, but the high schema coverage makes 3 the appropriate baseline.

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?

The description states a specific verb and resource: solving a Cloudflare challenge on the current page, including the "Just a moment..." page and Turnstile widget. It distinguishes the action from the sibling `open` flow by saying this is only needed when auto-solve was off or a widget appeared later.

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?

It gives an explicit condition for use: only when `open` ran with auto-solve off or a widget appeared later. That implies the when-not case as well, since auto-solved pages do not need this tool, and it names the relevant sibling flow.

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