xportalx

solve_captcha

Solve captchas on protected pages and extract content. Uses 2Captcha to bypass reCAPTCHA/hCaptcha, then Claude AI selects the best tool to retrieve content. Cost: 0.01 USDC

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": {
      "url": "<url>"
    },
    "name": "solve_captcha"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The captcha-protected URL to access
`intent`	No	What you want to extract from the page after solving captcha
`siteKey`	No	Site key for reCAPTCHA/hCaptcha (optional - auto-detected if not provided)
`captchaType`	No	Type of captcha to solve	recaptcha_v2

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: uses 2Captcha, bypasses reCAPTCHA/hCaptcha, pairs with Claude AI for content retrieval, and includes a cost of 0.01 USDC. This goes beyond basic functionality and reveals operational dependencies and pricing. It does not cover failure modes or rate limits, but the provided detail is valuable.

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?

The description is two sentences long, starts with the core purpose, and front-loads the most important information. Every clause is informative: purpose, method, delegation, and cost. There is no filler or redundancy, making it highly efficient.

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

Completeness3/5

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

The tool has 4 parameters, no output schema, and no annotations. The description explains the overall workflow and cost but leaves ambiguity about what exactly is returned (e.g., content directly or a tool recommendation) and lacks failure/success indicators. Given the lack of output schema, the description should clarify return format; 'extract content' is vague. It is adequate but not fully complete for a tool with these gaps.

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 description coverage is 100%, so the baseline is 3. The description does not add any parameter-specific meaning beyond the schema; it mentions 'extract content' which aligns with the intent parameter but does not elaborate on any parameter nuances. The schema already fully documents each parameter, so the description adds no incremental value here.

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 a specific verb and resource: 'Solve captchas on protected pages and extract content.' It distinguishes itself from sibling tools by being the only one addressing captcha bypass, and it names specific captcha types (reCAPTCHA/hCaptcha). This is unambiguous and action-oriented.

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?

The description implies usage context: 'on protected pages' and explains that after solving, Claude AI selects the best tool to retrieve content. This gives a clear scenario for when to use the tool. However, it does not explicitly mention alternatives or when not to use it, so it lacks full exclusions compared to a direct comparison.

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

All xportalx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?