Skip to main content
Glama

get_request_status

Retrieve a CAPTCHA solving result by request ID without triggering another paid request. Use it to check submission status or recover results.

Instructions

Recover a submission by request ID without making another paid request.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden and does disclose one genuinely useful behavioral trait: this call does not incur another paid request, i.e., it is a cheap/idempotent lookup rather than a re-execution. It says nothing about behavior for an unknown or expired request_id, latency/eventual-consistency of status, or whether a completed result is included.

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?

One short sentence with no filler, and the key scoping fact (no additional charge) is stated up front. It is efficient but so terse that it borders on under-specification rather than being optimally structured.

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 (one required parameter) and an output schema exists, so return values need not be described. Still, with zero annotations the definition should cover the missing-request case and clarify status-versus-result, which it does not.

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 parameter, so the schema contributes only a bare string type. The description names the key ('by request ID') but adds no format, origin (where the agent obtains it), or validity constraints, so it only marginally compensates for the coverage gap.

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?

The verb+resource ('Recover a submission by request ID') identifies a lookup keyed by request ID, but 'recover a submission' is ambiguous next to the tool name get_request_status and against siblings like get_task_result and get_task_result_wait. An agent cannot tell from the description whether it returns status only, the full result, or a cached payload.

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?

The phrase 'without making another paid request' implies the intended situation: re-checking something previously submitted so you don't pay twice. However, it never says explicitly when to use this versus re-submitting or versus the result-retrieval siblings, and gives no prerequisites (e.g., that the request_id must come from a prior submission).

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