Skip to main content
Glama
Sign In

Invoke Human Tool

by com.invokehumantool
OverviewDiscussionsAdmin

List interactive blocks

list_blocks
Read-onlyIdempotent

List the closed ih-ui block catalog. Pass labs true to include labs. names. Props, value shapes, events, merge rules, and examples are in https://invokehumantool.com/skills/invoke-human/references/language.md. This does not create a handoff.

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

Input Schema

NameRequiredDescriptionDefault
labsNoInclude labs. blocks. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds that the catalog is 'closed' and that calling it has no handoff side effect, which is meaningful given the sibling set, but says nothing about output shape, size, or caching.

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?

Very short and front-loaded with the core verb and resource. The middle sentence is a fragment ('names. Props, value shapes, events, merge rules...') and the external URL is doing a lot of unstated work, but nothing is padded.

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

Completeness3/5

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

With one optional parameter, no output schema and read-only annotations, the description is nearly sufficient. The gap is that it defers all substantive detail (block names, props, events) to an external reference the agent may not be able to fetch, and gives no hint of the return structure.

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 single parameter is fully documented in the schema; 'Pass labs true to include labs' merely restates it. No extra meaning, such as what labs blocks are versus stable ones, is added.

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: 'List the closed ih-ui block catalog.' The closing sentence 'This does not create a handoff' distinguishes it from the surrounding handoff siblings, though what an 'ih-ui block' actually is is only implied.

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 only selection guidance is the labs toggle and the negative signal that it does not create a handoff. It never says when an agent should call this instead of, or before, validate_ui or the send_*_handoff tools, so the routing decision is left 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