Skip to main content
Glama

hands.txt: a human proxy for AI agents

Is the human available?

service_status
Read-only

Tells whether new requests are being taken, when the human was last active, how long answers have been taking, and how many requests were done or declined.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish this as a read-only, non-open-world operation. The description adds useful behavioral detail by naming the status fields returned, including last activity, answer latency, and request outcomes. It does not explain freshness, how availability is determined, or any limitations on the reported metrics.

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 efficient sentence that front-loads the core availability check and then enumerates additional status details. Every clause adds distinct information with no redundant or filler wording.

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 parameterless status tool with read-only annotations, the description is largely complete: it identifies the operational details an agent would care about. It leaves some gaps around freshness and output format, but the absence of an output schema does not require extensive return-value documentation for this low-complexity tool.

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 has zero parameters, so there is no parameter semantics to document. The baseline score for a parameterless tool is appropriate here.

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 purpose with concrete details: it tells whether new requests are being taken, when the human was last active, response latency, and request counts. This is more than a restatement of the name. It does not explicitly distinguish itself from the sibling 'about' tool, but the operational status focus is clear.

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?

Usage is implied rather than stated: an agent can infer this should be checked before sending a new request or assessing availability. There is no explicit when-to-use guidance, no exclusions, and no named alternative such as 'about' for general service information.

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