Skip to main content
Glama

get_token

Solves supported reCAPTCHA task types and returns the resulting token through the direct token endpoint; verify the task schema first and note live solves may incur a charge.

Instructions

Solve a supported reCAPTCHA and return its token through the direct getToken endpoint.

Only the eight documented reCAPTCHA task types are eligible. Check the task schema first and choose one solve endpoint. Live solves may incur a charge.

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": "<task>"
    },
    "name": "get_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
app_idNo
request_idNo
callback_urlNo

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 disclosure burden. It usefully reveals that live solves may incur a charge and that eligibility is restricted, but says nothing about authentication, rate limits, failure modes, or whether charges apply to failed solves.

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?

Three short sentences, front-loaded with the verb-and-resource statement, then constraints, then cost warning. Minimal waste, though the phrase about the direct getToken endpoint adds little beyond what the name already conveys.

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 presence of an output schema relieves the description of explaining return values, and the pointer to the task schema partially covers the nested object. However, with a required nested task object and three optional routing parameters at 0% coverage, an agent still cannot confidently populate the call without a second lookup.

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 four parameters, and the description explains none of them. It points the agent to a separate task-schema lookup for the nested task object, which is a partial assist, but app_id, request_id, and callback_url remain entirely undefined in both schema and prose.

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: solve a supported reCAPTCHA and return its token via the getToken endpoint. It scopes the tool to eight documented reCAPTCHA task types, which meaningfully bounds it against generic siblings like create_task, but it never names a sibling to differentiate itself from.

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?

Gives explicit preconditions: check the task schema first, use only documented task types, and pick one solve endpoint rather than combining. Lacks an explicit when-not or a named alternative, so the routing guidance is implied rather than spelled out.

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