Skip to main content
Glama
Sign In

Captcha Solver

by io.github.mcp-dir
OverviewDiscussionsAdmin

captcha_get_result

Read-onlyIdempotent

Consulta o resultado de uma task de captcha já criada, pelo task_id. Não é cobrado (a cobrança ocorre na solve que criou a task).

Bulk support: accepts task_ids for batched execution.

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": {
      "task_id": "<task_id>"
    },
    "name": "captcha_get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
task_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context: no charge for this operation (billing happens at solve), and bulk support via task_ids. This goes beyond annotations and clarifies cost behavior, which is useful for an agent.

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, front-loaded with the core purpose, and includes a separate note for bulk support. Every sentence earns its place with no redundancy.

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?

Given the tool's simplicity (2 params, no output schema), the description covers the essential purpose, billing behavior, and bulk capability. It doesn't explain return format, but with no output schema and a straightforward query operation, this is acceptable. The main gap is parameter relationship details, but overall it's complete enough for an agent to use 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 description coverage is 0%, so the description must compensate. It explains task_id is the identifier for an existing captcha task and mentions task_ids for bulk execution, but doesn't detail format, constraints, or relationship between the two parameters (e.g., whether task_ids is an alternative to task_id). The description adds some meaning but leaves gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries the result of an existing captcha task by task_id, which is a specific verb+resource combination. It distinguishes from sibling solve tools by focusing on result retrieval rather than creation, though it doesn't explicitly name alternatives.

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 after a task is created via a solve tool, and notes billing occurs at solve time, not here. It mentions bulk support for batched execution, providing clear context. However, it doesn't explicitly state when not to use it or name alternative tools.

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

All Captcha Solver toolsInspect
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