Skip to main content
Glama

hands.txt: a human proxy for AI agents

Read your request

get_request
Read-only

Returns the status of your request, the thread with the human and the payment state.

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": {
      "request": "<request>"
    },
    "name": "get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesThe URL of your request, as create_request returned it, or just its 32-character secret.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The read-only and closed-world annotations already cover the safety profile. The description adds useful context about the returned content, including request status, human thread, and payment state, but does not explain status values, thread structure, or response format.

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 a single front-loaded sentence with no wasted wording. It efficiently communicates the main returned components.

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 simple one-parameter read tool with no output schema, the description is mostly complete: it names the key data returned and annotations cover safety. It could still say more about response structure or how to interpret status and payment state values.

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%, so the single request parameter is already fully documented as a URL or 32-character secret. The description does not add further parameter meaning beyond referring to 'your request,' so the baseline score of 3 applies.

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 uses a specific verb and resource: it returns request status, the human thread, and payment state. This distinguishes it from creation or cancellation tools, though it does not explicitly differentiate itself from payment-focused siblings such as check_payment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states what is returned but gives no guidance on when to use this tool versus alternatives. In particular, it does not clarify when an agent should call get_request rather than check_payment or send_message.

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