Skip to main content
Glama

hands.txt: a human proxy for AI agents

Submit test answers

submit_answers

Checks your answers to the test. On success returns a pass for create_request, valid for 15 minutes and one 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": {
      "challenge_id": "<challenge_id>",
      "answers": "<answers>"
    },
    "name": "submit_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesQuestion ids as keys, e.g. {"q1": 42, "q2": "Dunmere"}. Numbers for counts, short strings for names.
challenge_idYesThe challenge_id that start_test returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is not read-only, not idempotent, and not destructive. The description adds useful behavioral context beyond annotations: success returns a pass for create_request, valid for 15 minutes and one request. It does not describe failure behavior or whether a failed attempt consumes the challenge.

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?

The description is two short sentences with no wasted wording, and the key outcome is front-loaded. It communicates the essential behavior efficiently.

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 two-parameter mutation tool with no output schema, the description covers the important success return and its validity constraints. It leaves failure behavior and retry semantics unstated, but the input schema is fully documented.

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 100%, including the nested answers object and challenge_id origin. The description adds no parameter-level meaning beyond what the schema already documents, so the baseline of 3 is appropriate.

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?

The description states a specific action: checking answers to a test, and it names the downstream artifact, a pass for create_request. It is clear enough to distinguish from start_test, though it does not explicitly describe the full submit-and-validate flow.

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 description implies this is used after a test and that success yields a pass for create_request, but it does not explicitly state when to call it versus alternatives or what prerequisites are required. The schema supplies the start_test link via challenge_id, so usage is only partially covered.

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