Skip to main content
Glama

hands.txt: a human proxy for AI agents

Write to the human

send_message

Adds a message to your request, for example an answer to the human's question. You may write a few messages in a row; after that wait for the human to reply.

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>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesYour message.
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

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world write, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: it is a conversational, multi-turn channel where bursts of a few messages are acceptable followed by a wait for the human. It says nothing about delivery timing, visibility, or what happens if you keep writing, so it stops short of 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?

Two short sentences, front-loaded with the action and followed by the pacing rule. Nothing is redundant or padded.

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 write tool with full schema coverage, no output schema needed, and annotations covering the safety profile, this is nearly sufficient. The remaining ambiguity is what sending returns and whether the human's reply arrives asynchronously, but the 'wait for the human to reply' line implies the conversational loop.

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% and the 'request' parameter is fully documented in the schema, including the 32-character secret alternative. The description adds only mild framing for 'message' ('an answer to the human's question') and no format, length, or content guidance beyond what the schema states, so the baseline 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 verb and object ('Adds a message to your request') and situates it with a concrete example ('an answer to the human's question'). An agent can tell this is a write-to-conversation tool rather than a request lifecycle tool like create_request or get_request, though it never explicitly contrasts itself with submit_answers.

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?

Gives clear situational context (answering the human's question) plus practical pacing guidance: a few messages in a row are fine, then wait for a reply. There are no explicit exclusions or named alternatives, which keeps it short of a 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