Skip to main content
Glama
usernamexiaozhang

camoufox-versatile-mcp

auto_solve_captcha

Auto-detect and solve Cloudflare captcha challenges on the current page, with verification that protected content loads.

Instructions

Auto-detect and solve a captcha challenge on the current page.

Wraps camoufox_captcha.solve_captcha (same library as project test.py). Probes the page for captcha indicators, clicks through the challenge, and verifies the protected content actually loaded.

Args: captcha_type: Captcha provider, e.g. "cloudflare". The library is future-proof; new providers (hcaptcha, recaptcha, ...) will be supported as camoufox_captcha adds them — pass the new name here. challenge_type: "auto" (recommended), "interstitial", or "turnstile". "auto" probes both variants and solves whichever is detected. ready_delay: Seconds to wait for the captcha iframe to mount before attempting to click. expected_content_selector: Optional CSS selector to wait for after solving. solve_attempts: Maximum solve attempts (passed to solver). solve_click_delay: Seconds to wait after clicking so the provider can validate the click. wait_checkbox_attempts: Maximum polls to wait for the checkbox to appear. wait_checkbox_delay: Seconds between checkbox-wait polls. checkbox_click_attempts: Maximum click attempts on the checkbox itself. attempt_delay: Seconds between top-level solve attempts. verify: Re-read page.content() after solving and confirm the provider's challenge marker is gone. Strongly recommended.

Returns: dict with detected, challenge_type_used, solved, attempts, verified, final_url, error (if any).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verifyNo
ready_delayNo
captcha_typeNocloudflare
attempt_delayNo
challenge_typeNoauto
solve_attemptsNo
solve_click_delayNo
wait_checkbox_delayNo
wait_checkbox_attemptsNo
checkbox_click_attemptsNo
expected_content_selectorNo
Behavior4/5

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

Despite no annotations, the description details the process: probes page, clicks, verifies. It also mentions the return dictionary structure. However, it does not disclose potential side effects or error scenarios, but the behavioral traits are well covered.

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?

The description is well-structured with clear sections (overview, Args, Returns) and front-loaded purpose. Though lengthy, each sentence adds value, but minor redundancy exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (11 parameters, no output schema, no annotations), the description is thorough. It explains return values, parameter behaviors, and verification steps, making it highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides extensive parameter explanations, including purpose, recommended values, and future extensibility. This adds significant meaning beyond the schema.

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 clearly states the tool's purpose: 'Auto-detect and solve a captcha challenge on the current page.' It specifies the verb (solve) and resource (captcha) and distinguishes from sibling detect_captcha by explicitly mentioning solving and referencing the underlying library.

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 description implies usage when a captcha is encountered but does not provide explicit guidance on when to use this tool versus alternatives like detect_captcha. There is no 'when-not' or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/usernamexiaozhang/camoufox-versatile-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server