svipall

Overview Schema Source Related Servers Discussions Admin

solve_recaptcha_v2

Solve reCAPTCHA v2 challenges from a sitekey and page URL to return a gRecaptchaResponse token, or a taskId to poll while a person solves it.

Instructions

Solve a reCAPTCHA v2 challenge from its sitekey and pageUrl and return the gRecaptchaResponse token. Use only when you will submit the token yourself from the same session and address; to read the page behind the challenge use solve_and_continue. Returns the token, or a taskId to follow with captcha_status while a person solves it.

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": {
      "sitekey": "<sitekey>",
      "pageUrl": "<pageUrl>"
    },
    "name": "solve_recaptcha_v2"
  }
}

Input Schema

Name	Required	Description
`pageUrl`	Yes	The page the widget is on.
`sitekey`	Yes	The widget's site key, from the page's data-sitekey attribute.
`invisible`	No	The invisible variant, with no checkbox. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses a non-obvious constraint (same session/address), the dual return path (token or taskId to poll via captcha_status), and that a human may be involved. It doesn't mention credits, rate limits, or timeouts, so it stops short of a 5.

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?

Three sentences, each load-bearing: what it does, when to use it (with the alternative), and what comes back. Front-loaded with the operation and inputs.

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?

With no output schema, the description carries the return-value burden and does so ('the token, or a taskId to follow with captcha_status'). Combined with the session constraint and routing to solve_and_continue, an agent has everything needed to invoke and follow up correctly.

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 covereage is 100% and the schema already documents pageUrl and sitekey with source detail (data-sitekey attribute). The description names the same two inputs but adds nothing about the optional 'invisible' flag, so it only matches, not exceeds, 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?

States a specific verb and resource ('Solve a reCAPTCHA v2 challenge') plus the inputs (sitekey, pageUrl) and the artifact produced (gRecaptchaResponse token). It also names the sibling it must not be confused with (solve_and_continue), so an agent can separate them 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given: 'Use only when you will submit the token yourself from the same session and address; to read the page behind the challenge use solve_and_continue.' This supplies both the inclusion condition and the named alternative.

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