Skip to main content
Glama

Your AIs ask you on your phone: approvals, choices, feedback

Get answers from a call to people

ask_people_results
Read-onlyIdempotent

Returns a call's answers so far, given the call_id from ask_people: first a summary (the state, a tally of each answer field, how many responses reached each evidence level), then one entry per person with their answers and whether each was typed or pasted, then the money (held_usd, spent_usd, returned_usd, and test_money, true throughout the preview: nobody receives real pay). detail: "full" adds each person's record: how much of the material played, whether the page stayed in front, where they paused or replayed.

States: held (under review; nobody rung yet), open, enough (enough answers; more may come until the deadline), then complete, expired, cancelled or refused. Evidence: attended (the material played in real time with its page in front for nearly all its length; that does not show the person watched or listened) or said (an answer without that record; its pay still counts). No level shows that an answer was formed without help.

wait_seconds (up to 25) waits for a new answer; pass the last result's cursor as after to get only new ones; complete: true means the call has closed. Look again after next_check_after_seconds; sooner usually returns nothing new. Simulated answers carry simulated: true and begin "[simulated] ".

Example: {"call_id": "call_...", "after": "", "wait_seconds": 25}

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": {
      "call_id": "<call_id>"
    },
    "name": "ask_people_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoThe cursor from the last result; only newer answers come back.
detailNo"full" adds each person's record and what they were shown.
call_idYesThe call_id ask_people returned.
wait_secondsNoWait up to this many seconds for a new answer (default 20).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only establish that this is a safe, idempotent, closed-world read. The description goes far beyond that: it defines the state machine (held/open/enough/complete/expired/cancelled/refused), the evidence levels and what they do and do not prove, that `test_money` is true throughout the preview with nobody receiving real pay, and that simulated answers are flagged with `simulated: true` and a bracketed prefix. That is exactly the behavioral context annotations cannot convey.

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

Conciseness3/5

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

The first sentence is well front-loaded with the core behavior and the polling mechanics that actually affect the call are kept. But a large block then enumerates return values — every state, both evidence levels, and each money field — which an output schema already covers, making the description noticeably longer and denser than the decision-relevant content requires.

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?

For a polling endpoint with four parameters, an output schema, and a non-obvious domain vocabulary, nothing an agent needs is missing: cursor looping, wait cap, terminal state, simulated-answer marker, and a worked example call are all present. The extra return-value explanation is redundant against the output schema but does not leave any gap.

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 already 100%, so the baseline is 3, but the description adds real meaning: `after` is specifically the cursor from the previous result, `wait_seconds` is capped at 25, and `detail: "full"` is explained as adding the person's record (how much material played, whether the page stayed in front, pauses/replays) rather than just restating the enum. It even explains the output-side `complete: true` that drives the polling decision, though it does not restate the default for wait_seconds that the schema carries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ("Returns a call's answers so far") and ties the required call_id back to the sibling tool that produced it (ask_people). An agent can immediately separate this read/results tool from ask_people, ask_people_cancel, and the other siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operational guidance: pass the last result's cursor as `after` to get only new answers, `wait_seconds` (up to 25) waits for a new answer, and re-poll after `next_check_after_seconds` because polling sooner usually returns nothing. What it lacks is an explicit statement of when not to call it or how it relates to siblings like ask_people_panel, so it falls short of a full 5.

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.