Skip to main content
Glama

Make a panel of invited people

ask_people_panel

Makes a panel, a named group of people the account owner invites, and returns its panel_id and a join link for your user to share. Each person joins on their own phone, states that they are an adult, is told what is recorded while they answer (how much played, whether the page stayed in front, pauses and replays, typed or pasted), chooses when they can be rung, and can leave at any time. Calls with pool "panel:<panel_id>" then reach only them, and cost nothing at zero pay. On a panel of fewer than five, both sides are told that answers cannot be anonymous.

Use it only when your user asks to set up a group of people they will invite themselves; nobody is added without joining. Any key can make a panel, a free test key too (with no key, the error says how to get one); calls with its pool ring the people who joined, when they are available. Your user's own pages, builds, audio and video reach them after they are read: by a model in seconds for a plain page or build, otherwise by a person at person.tools. A retry with the same idempotency_key returns the same panel; without one, a retry makes a second panel.

Example: {"name": "album-listeners", "idempotency_key": "panel-1"}

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe panel's name, for you (your people see asker_name). The same name again returns the same panel.
asker_nameNoYour user's own name, or their company's: the one their people know. Each person sees it before they take a call, so a name your user did not give would mislead them.
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asker_name / description
      Previous value: -"The name your people know you by; each person sees it before they take a call."New value: +"Your user's own name, or their company's: the one their people know. Each person sees it before they take a call, so a name your user did not give would mislead them."
  2. Changed1 schema field changed
    • changedInput schema / properties / asker_name / description
      Previous value: -"The name your people know you by, shown to them as \"<name> (named by the asker; not checked by person.tools)\". Nobody can join until it is set; send it again with the same name to set it later."New value: +"The name your people know you by; each person sees it before they take a call."
  3. Changed2 schema fields changed
    • addedInput schema / properties / asker_name
      Added value: +{
      +  "description": "The name your people know you by, shown to them as \"<name> (named by the asker; not checked by person.tools)\". Nobody can join until it is set; send it again with the same name to set it later.",
      +  "maxLength": 60,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"The panel's name (live keys only)."New value: +"The panel's name, for you (your people see asker_name). The same name again returns the same panel."
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only establish it is not read-only, is open-world, and not inherently idempotent), the description discloses the full consent flow: each person states adulthood, is told what is recorded, chooses when to be rung, and can leave. It also explains idempotency behavior, key requirements, and the anonymity caveat on panels under five.

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?

It front-loads purpose well and ends with a useful example, but it is long and dense. The parenthetical recording detail and the "model in seconds... person at person.tools" sentence add context at the cost of tightness.

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 values need little explanation, yet the description still names panel_id and the join link. It covers consent, keys, and anonymity thoroughly; the only incompleteness is the mild name-vs-idempotency retry inconsistency that could confuse an agent about when a duplicate panel is created.

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 67%. The description adds real meaning for asker_name ("Each person sees it before they take a call, so a name your user did not give would mislead them") and explains idempotency_key's retry behavior. One caveat: the description says a retry without a key makes a second panel, while the schema says the same name returns the same panel, a minor internal inconsistency.

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: "Makes a panel, a named group of people the account owner invites, and returns its panel_id and a join link." The scope (invited, self-joining group) and the pool routing ("calls with pool panel:<panel_id> reach only them") set it apart from a generic ask_people call, though it never names a sibling directly.

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?

"Use it only when your user asks to set up a group of people they will invite themselves; nobody is added without joining" gives explicit when-to-use plus an exclusion. It also covers key requirements (free test key acceptable). It does not explicitly contrast with ask_people or ask_people_cancel, so the alternative-routing is implied rather than spelled out.

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.