Skip to main content
Glama

Turingate

Submit reverse-CAPTCHA answers

submit_answers

Submit answers for a challenge from get_challenge. answers maps task id to a short answer, e.g. {"t1": "42", "t2": "violin"}.

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": {
      "challenge_id": "<challenge_id>",
      "answers": "<answers>"
    },
    "name": "submit_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYes
challenge_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

The only annotation is openWorldHint=false, so the description carries nearly the full behavioral burden, and it does not disclose whether submission is one-shot or repeatable, what happens to a partially wrong answer set, whether a verification step follows, or any rate/attempt limits. It adds the answer-value format, but the mutation outcome is left opaque.

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?

Two short sentences, action first, with the illustrative example earning its place by disambiguating the nested object shape. No filler.

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?

Input shape is adequately covered, but with no output schema the description should say what a submission returns (pass/fail, per-task feedback) and what state it changes. For a submit tool in a multi-step readiness flow, that gap matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and one parameter is a nested object, so the description must compensate. It does so well for 'answers' by stating the task-id-to-short-answer mapping and giving a concrete two-entry example; 'challenge_id' is only inferable from 'a challenge from get_challenge' rather than stated outright.

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?

Specific verb and resource: 'Submit answers for a challenge', and it names the sibling that produces the challenge (get_challenge), so the agent can place it in the workflow. It stops short of saying what submission achieves (verification/scoring), so it is clear but not fully self-locating.

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 'for a challenge from get_challenge' implies the required ordering — call get_challenge first — which is useful implicit guidance. There is no explicit when-to-use/when-not, no mention of retries or whether multiple submissions are allowed.

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.