Skip to main content
Glama
Sign In

Invoke Human Tool

by com.invokehumantool
OverviewDiscussionsAdmin

Read the current handoff

get_handoff_state
Read-onlyIdempotent

Read one open or completed handoff this key can see: status, the blocks as stored, answers already on the server, and each section. A section is complete when its logs and required inputs are done. Display blocks do not hold a section open. Pending is a successful read. This does not push and does not change the handoff.

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": {
      "id": "<id>"
    },
    "name": "get_handoff_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHandoff id, hnd_...

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, but the description adds substantive behavioral detail: pending is a valid successful result, display blocks do not hold a section open, section completion depends on logs and required inputs, and the call neither pushes nor changes the handoff. It also scopes visibility to what this key can see.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four dense sentences, front-loaded with what is read and followed by important semantics about section completion, pending reads, and lack of side effects. Each sentence adds useful domain context, with only minor list-like density.

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 one-parameter read tool with rich annotations but no output schema, the description names the main returned concepts and explains section-completion and pending-state semantics. Exact response shape and possible status values remain unspecified, so it is helpful but not exhaustive.

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 schema already documents the sole id parameter as a handoff id in hnd_... form. The description adds visibility scope ('this key can see') but no further id syntax, lookup, or filtering semantics beyond the schema.

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?

States a specific verb and resource: reading one open or completed handoff visible to this key, and enumerates returned components such as status, blocks, answers, and sections. It does not explicitly distinguish itself from sibling tools like get_handoff_status, get_handoff_result, or get_handoff_history.

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?

Gives implied usage context by saying it reads one open or completed handoff and that pending is a successful read. However, it never states when to choose this tool over get_handoff_status, get_handoff_result, get_handoff_history, or wait_for_handoff, leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Invoke Human Tool toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources