Skip to main content
Glama

wait_for_result

Wait for a pending CapSolver solve result using an existing task ID. If the timeout expires, keep the task ID and avoid creating a new paid task.

Instructions

Wait for the result of a pending CapSolver solve using its existing task ID.

Timeout keeps the task ID and never recreates a paid task.

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

Input Schema

NameRequiredDescriptionDefault
task_idYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the key cost-safety property that a timeout preserves the task ID and never recreates a paid task, but it says nothing about whether the call blocks, how long it polls, what is returned or raised on timeout, or the failure modes.

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 sentences, front-loaded with the core action, with no filler. The second sentence is slightly elliptical ('Timeout keeps the task ID' rather than 'on timeout...'), but it still lands the point.

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

Completeness3/5

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

The tool is simple (two parameters, one required) and an output schema exists, so return-value documentation is rightly omitted. Still, for a blocking wait operation the description leaves open what happens at timeout and whether the call is safe to retry, which matters for an agent deciding how to sequence it.

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 explain both parameters. It adds real meaning for task_id (an existing ID belonging to a pending solve) and hints at the consequence of timeout, but the timeout parameter's units, valid range, and default behavior are never clarified.

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 gives a specific verb and resource: wait for the result of a pending CapSolver solve, identified by its existing task ID. That is clear enough to act on, but it does not distinguish this tool from siblings such as get_task_result_wait and get_task_result, which sound like they cover similar ground.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must already have a task ID from a prior create, and the task must still be pending. The description never states when to choose this over get_task_result or get_task_result_wait, and it does not say what to do if the task is already finished or failed.

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