svipall

Overview Schema Source Related Servers Discussions Admin

solve_turnstile

Solve a Turnstile challenge from its sitekey and pageUrl to get the token you submit yourself in the same session. Returns the token, or a taskId to track with captcha_status.

Instructions

Solve a Turnstile challenge from its sitekey and pageUrl and return the token. Use only when you will submit the token yourself from the same session and address, such as a form posted with web_fetch method=POST; 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_turnstile"
  }
}

Input Schema

Name	Required	Description	Default
`pageUrl`	Yes	The page the widget is on.
`sitekey`	Yes	The widget's site key, from the page's data-sitekey attribute.

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?

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description carries the real behavioral burden and does so: it discloses the dual return mode (token vs. taskId) and that a taskId must be polled via captcha_status while a person solves it. It also reveals the session/address constraint, which is non-obvious. It stops short of stating timeout/failure semantics.

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 tightly packed sentences with the core action front-loaded, then the routing condition, then the return values. No filler; every clause conveys decision-relevant information.

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?

For a 2-param, no-output-schema tool, the description covers the action, the disambiguating alternative, the submission constraint, and the two possible return shapes including how to follow up on a taskId. Nothing an agent needs to invoke it correctly is missing.

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%, with pageUrl and sitekey already documented (including the data-sitekey origin). The description names both parameters but adds no format, syntax, or sourcing detail beyond the schema, so baseline 3 applies.

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+resource (solve a Turnstile challenge) plus the inputs and output (token), and explicitly distinguishes itself from the sibling solve_and_continue. An agent can identify this tool from siblings 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?

Gives an explicit when-to-use condition ('only when you will submit the token yourself from the same session and address, such as a form posted with web_fetch method=POST') and names the alternative (solve_and_continue) with the condition that selects it (reading the page behind the challenge).

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