Skip to main content
Glama

hands.txt: a human proxy for AI agents

File a request for the human

create_request

Files your request. A person reads it exactly as you write it, so be concrete: what to do, where, and what you want back. Do not include secrets. Returns the private URL of the request; keep it.

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": {
      "pass": "<pass>",
      "task": "<task>",
      "reason": "<reason>"
    },
    "name": "create_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional. What the human should call you.
passYesThe pass that submit_answers returned.
taskYesWhat you need done.
reasonYesWhy you need it.
deadlineNoOptional. For example: within two days.

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 openWorldHint=true, readOnlyHint=false, and destructiveHint=false. The description adds valuable context beyond those: a human reads the content verbatim, secrets must be excluded, and the return value is a private URL to retain. It does not discuss latency or approval outcomes, which keeps it from a 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?

Three short sentences, front-loaded with the core action, followed by authoring guidance and the return-value note. No sentence is filler; the 'do not include secrets' warning is compact and high-value.

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 five-parameter mutation tool with full schema coverage and no output schema, the description covers the essential unknowns: human review, secret hygiene, and the returned private URL. A note on the 'pass' token's dependency on submit_answers would make it fully complete.

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 coverage is 100%, so all five parameters are already documented, establishing a baseline of 3. The description adds content guidance for the task field ('what to do, where, and what you want back') but does not explain the 'pass' parameter's origin or how deadline is interpreted.

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 opens with a specific verb and resource: 'Files your request,' and the title clarifies the recipient is a human. An agent can tell this creates a new request rather than retrieving or canceling one, though the sibling names are not explicitly referenced.

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?

Guidance focuses on how to write the request ('be concrete: what to do, where, and what you want back') rather than when to choose this tool over siblings like send_message or get_request. Usage is implied by the verb, but no alternative or exclusion is stated.

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