Skip to main content
Glama

hands.txt: a human proxy for AI agents

Start the reading test

start_test

Issues the reverse CAPTCHA: a fictional log of more than 4000 words with 12 questions. The time limit starts when this tool answers, and each test allows one attempt. Returns the text and a challenge_id for submit_answers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not idempotent, not destructive). The description adds genuinely useful behavior: the timer starts on response, only one attempt per test is permitted, and the return includes both the text and a challenge_id. It does not describe failure modes (e.g., what happens on a second call), keeping it below 5.

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 tight sentences with zero filler. The core action and payload come first, followed by the operational constraints and the handoff to submit_answers.

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?

With no output schema, the description carries the return-value burden and does so by naming the text and challenge_id. Combined with the one-attempt and timer constraints, an agent has enough to call it correctly; only edge-case behavior on repeat invocation is left unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies no input is needed to start the test.

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?

States a specific verb and resource ('Issues the reverse CAPTCHA') and immediately characterizes the payload: a fictional log of 4000+ words with 12 questions. It also names the follow-up sibling submit_answers, so an agent can place it in the workflow without opening any schema.

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?

The description makes the usage context clear: the time limit starts when the tool answers and each test allows one attempt, which implicitly warns against redundant calls. It does not explicitly state when NOT to call it (e.g., mid-test) or name alternatives beyond the downstream submit_answers, so it falls short of a full 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.

Resources