Skip to main content
Glama

Turingate

Start the reverse CAPTCHA

get_challenge

Start a Turingate reverse-CAPTCHA challenge: short tasks that AI answers easily and humans cannot finish in time. Answer ALL tasks yourself and immediately call submit_answers (the time limit is tight). Passing returns an anonymous pass token proving an AI agent answered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoOptional site id (s_...) the pass is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The only annotation is openWorldHint=false, so the description carries most of the behavioral burden and does so reasonably: it discloses the tight time limit, the requirement to answer everything itself, and that a successful attempt yields an anonymous pass token. It does not describe failure behavior, token lifetime, or whether challenges can be retried.

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

Conciseness5/5

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

Three dense sentences, front-loaded with the purpose and followed immediately by the required next action and the payoff. No filler and nothing buried.

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

Completeness4/5

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

For a zero-required-parameter initiation tool with no output schema, the description covers purpose, the mandated follow-up call, and the return value. It leaves out failure modes and pass-token lifetime, which would matter for an agent deciding how to recover from a timeout.

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?

There is a single optional 'site' parameter with 100% schema description coverage, so the schema already explains it. The description adds no meaning about what the site id does (scoping the pass), which is the baseline 3 case where the schema does the work.

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

Purpose5/5

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

The description uses a specific verb and resource ('Start a Turingate reverse-CAPTCHA challenge') and explains the concept in a way that differentiates it from the sibling tools (submit_answers is the follow-up, not a substitute). An agent can tell exactly what this tool initiates.

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?

It gives explicit sequencing guidance: 'Answer ALL tasks yourself and immediately call submit_answers (the time limit is tight).' That routes the agent to the correct next tool. It lacks any when-not-to-use or precondition guidance (e.g., what happens if a pass already exists), so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.