Skip to main content
Glama

Plures

Get the human answer

get_human_answer
Read-only

Check on a task sent with ask_humans and return the verified people's answer once it's ready.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_human_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task_id ask_humans returned
wait_secondsNoHow long to wait if it's still pending. Default 0

Output Schema

NameRequiredDescriptionDefault
kindNo
meanNo
modeYes
labelYes
routeYes
votesYes
answerYes
statusYes
answersYes
reasonsNo
signoffNo
task_idYes
agreementYes
contestedNo
with_teamYes
decided_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that answers are 'verified' (a trust property worth knowing), but it doesn't say what is returned while the task is still pending, whether repeated calls are expected, or how wait_seconds changes the outcome — even though those are the behaviors that would trip an agent up.

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?

One sentence, no filler, and the dependency on ask_humans is front-loaded where the agent will read it first.

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?

An output schema exists, so return shape doesn't need explaining, and the description covers the task lifecycle link to ask_humans with the 100%-covered parameters. What's missing is only the not-ready/polling expectation, which is a small but real gap for a retrieval tool with a wait_seconds parameter.

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 description coverage is 100%, and the description adds nothing beyond it — the link between task_id and ask_humans is already stated in the schema's own parameter description. Baseline 3 is the right call.

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 ('check on a task', 'return the verified people's answer') and names the sibling it pairs with (ask_humans), which lets an agent tell it apart from the ask/cancel flow. It stops short of stating the retrieval/polling semantics, so not a 5.

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 description implies use after a task was sent with ask_humans, which is real routing guidance, but it gives no when-not guidance and doesn't mention cancel_human_task or what to do if the answer never becomes ready. The wait_seconds default and cap live only in the schema.

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.