Skip to main content
Glama

get_task_result

Retrieve the result of a known CAPTCHA task while respecting query budgets, spacing, and the task's original expiry.

Instructions

Query one known task, respecting shared query budgets, spacing and its original expiry.

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

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose non-obvious traits: shared query budgets, request spacing, and that the task's original expiry is respected. These are exactly the constraints an agent needs to avoid hammering the endpoint, though the consequence of hitting a budget or an expired task is left unstated.

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?

A single front-loaded sentence with no filler; the limiting constraints appear immediately. "Its original expiry" is slightly ambiguous about whose expiry and what happens at that 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?

An output schema exists, so return values need no explanation, and the rate/spacing/expiry behavior is covered. Still missing is what happens on an unknown, expired, or not-yet-finished task — a meaningful gap for a single-parameter polling tool.

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% for the single required task_id, so the description must compensate. "One known task" and "its original expiry" imply task_id identifies an existing task subject to expiry, which adds some meaning, but it never says what form the identifier takes.

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

Purpose3/5

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

"Query one known task" names a verb and resource, but it never says the tool returns the task's result, completion status, or output payload — the agent has to infer that from the name. It also does not distinguish itself from siblings like get_task_result_wait or wait_for_result.

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?

The phrase "one known task" implies a precondition that task_id must reference an already-created task, which is mild guidance. There is no explicit statement of when to call this versus get_task_result_wait or wait_for_result, and no exclusions or failure conditions are given.

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