Skip to main content
Glama

get_task_result_wait

Waits for a CapSolver task to finish and returns its result so you can retrieve CAPTCHA output after submitting a task.

Instructions

Wait on the original CapSolver task. Provider query limits still apply.

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": "get_task_result_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
timeout_secondsNo
poll_interval_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds one real caveat — that provider query limits still apply — but says nothing about what happens when timeout_seconds expires (error, null, partial result), how poll_interval_seconds affects behavior, or whether the call blocks the whole time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler. The brevity is efficient, though it borders on under-specification rather than tight writing.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But for a blocking, polling-style tool with three undocumented parameters, no annotations, and no timeout or error semantics, the definition leaves out information an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters: task_id, timeout_seconds, and poll_interval_seconds are entirely undocumented. The description adds no meaning to any of them; the phrase "provider query limits still apply" only loosely gestures at polling frequency without explaining the poll_interval_seconds or timeout_seconds tradeoff.

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?

States a specific verb and resource: "Wait on the original CapSolver task." An agent can infer this is a blocking wait against a previously created CapSolver task. It does not, however, differentiate itself from plausible siblings such as wait_for_result or get_task_result, so it stops short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of when to prefer this over get_task_result (non-blocking) or wait_for_result, and no prerequisites such as requiring an already-created task. The only hint is "original CapSolver task," which is not an explicit alternative condition.

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