Skip to main content
Glama

Invoke Human Tool

by com.invokehumantool
OverviewDiscussionsAdmin

Forward a handoff

delegate_handoff
Destructive

Forward a handoff you can reassign and invite the new recipients. release defaults to true and drops your own duty to answer down to view. Set release to false to keep that duty. The default is destructive.

Input Schema

NameRequiredDescriptionDefault
idYesHandoff id, hnd_...
noteNo
releaseNoDefaults to true.
recipientsYes
await_answerNoLegacy alias for mode sync. mode wins when both are set. When this client declares the MCP Tasks extension, true returns a task and the client delivers the same JSON as get_handoff_result once they submit. Omit it to get the handoff id immediately. Clients that do not declare Tasks ignore this flag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / await_answer / description
      Previous value: -"Set true to wait for the human's answer. When this client declares the MCP Tasks extension, the call returns a task and the client delivers the same JSON as get_handoff_result once they submit. Omit it, or pass false, to get the handoff id immediately and keep working. Clients that do not declare Tasks ignore this flag and return the handoff id, same as today."New value: +"Legacy alias for mode sync. mode wins when both are set. When this client declares the MCP Tasks extension, true returns a task and the client delivers the same JSON as get_handoff_result once they submit. Omit it to get the handoff id immediately. Clients that do not declare Tasks ignore this flag."
  2. Changed1 schema field changed
    • addedInput schema / properties / await_answer
      Added value: +{
+  "description": "Set true to wait for the human's answer. When this client declares the MCP Tasks extension, the call returns a task and the client delivers the same JSON as get_handoff_result once they submit. Omit it, or pass false, to get the handoff id immediately and keep working. Clients that do not declare Tasks ignore this flag and return the handoff id, same as today.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes further by explaining what is actually destroyed: your own answer duty drops to view when release is true. It also discloses the MCP Tasks interaction for await_answer and the fallback of returning the handoff id immediately, which no structured field conveys.

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?

Four short sentences, front-loaded with the action and then the parameter consequence, with no filler. The opening sentence is slightly tangled ('a handoff you can reassign'), but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, open-world mutation with a rich schema and full annotations, and the description covers the missing pieces: the destructive default, how to opt out of it, and what await_answer returns. There is no output schema, yet the return behavior is still described, so an agent has what it needs to call it safely.

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?

Schema coverage is 60%, and the description compensates for the most consequential gap by explaining the real effect of the release flag rather than just repeating its default. It also clarifies the return behavior tied to await_answer. The note field and some recipient target fields remain undocumented in either place.

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 first sentence gives a specific verb and resource ('Forward a handoff') plus the two capabilities that distinguish it (reassign, invite new recipients). It is clear enough to separate from send_handoff or share_handoff in intent, but it never names those siblings to make the boundary explicit.

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?

The release semantics ('defaults to true and drops your own duty to answer down to view. Set release to false to keep that duty') imply when to pick which behavior, which is real usage guidance. However, there is nothing about when to forward versus share or send a handoff, and no prerequisites or exclusions are stated.

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