svipall

Overview Schema Source Related Servers Discussions Admin

report_captcha

Report whether a captcha solution was accepted or rejected, by task ID, to improve future solving strategies on that route.

Instructions

Report whether a captcha answer worked (good=true) or was rejected (good=false), by taskId. Call it after submitting a token from solve_turnstile, solve_recaptcha_v2 or solve_hcaptcha: the outcome orders the strategies tried next time on that route, so an unreported rejection is repeated.

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": {
      "taskId": "<taskId>",
      "good": "<good>"
    },
    "name": "report_captcha"
  }
}

Input Schema

Name	Required	Description
`good`	Yes	true: the site accepted the answer. false: it was rejected.
`note`	No	What the site said, if anything; kept with the outcome.
`taskId`	Yes	The `taskId` a solve_* tool returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses a real behavioral trait beyond the annotations: outcomes order the strategies tried next time on that route, so the effect is persistent and feedback-driven. Annotations only say readOnlyHint=false. It could note idempotency or overwrite behavior, but the feedback-loop effect is the key non-obvious trait and is covered.

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?

One dense sentence states the action, the payload, the key, and the reason to call it. No filler, and the routing instruction is front-loaded.

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?

Complete enough for a small 3-param mutation tool with no output schema: action, post-condition, and the consequence of omission are all present. It stops short of 5 only because return behavior and error handling are not mentioned.

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 schema already documents good, note, and taskId fully. The description adds only the good semantics, which the schema also states. Baseline 3 is correct when the schema does the work.

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 (report) and resource (captcha outcome), with the boolean semantics spelled out (good=true worked, good=false rejected) keyed by taskId. The relationship to the solve_* family is explicit, distinguishing it from the solve tools.

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?

Explicitly says when to call it: after submitting a token from solve_turnstile, solve_recaptcha_v2, or solve_hcaptcha. Also gives the when-not consequence: an unreported rejection is repeated because it feeds strategy ordering, which is a strong reason to always report.

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