Skip to main content
Glama

List a poll's answers

list_calls
Read-onlyIdempotent

Every call behind one of your polls' results, oldest first: the prompt and system prompt exactly as sent, every setting, the raw reply, how it was read, which model answered, tokens and charges, and read_market (whether its search read a prediction market). Filter by run. as_of reads each answer as it was read then. Only the poll's owner reads its calls, public or not: a public poll's readers get its results (get_results), which quote a sample reply per question. (GET /api/v1/polls/{id}/calls)

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

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
as_ofNoRead as things stood at this moment (RFC 3339): only runs this reader could have seen by then, each answer as it was read then.
limitNoCalls per page, 1 to 500.
cursorNonext_cursor from the previous page, unchanged.
run_idNoOnly this run's calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: access is owner-only regardless of poll visibility, results are ordered oldest first, and as_of converts the read into a historical view. It also discloses the sensitive payload (raw replies, token/charge data), which matters for an agent deciding whether to surface it.

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?

The core scope is front-loaded in the first clause and the enumeration of returned fields earns its length by telling the agent how rich the payload is. The parenthetical endpoint and the long field list make it dense, but nothing is redundant with the annotations or schema.

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?

With no output schema, the description carries the return-shape burden and does so by naming every returned field group. Combined with the auth caveat, ordering, historical-read mode, and schema-documented pagination, an agent has everything needed to call this correctly.

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 100%, so the baseline is 3; the description still adds conceptual meaning on top of the schema by explaining that as_of reads 'each answer as it was read then' and that run_id narrows to a single run. It doesn't add anything for limit/cursor, but those are adequately documented in the schema.

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 description names the resource precisely ('every call behind one of your polls' results') and enumerates exactly what each returned item contains — prompt, system prompt, settings, raw reply, model, tokens/charges, read_market. It also explicitly distinguishes itself from get_results, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

It states when to use this tool ('Only the poll's owner reads its calls, public or not') and names the alternative path for the other audience ('a public poll's readers get its results (get_results), which quote a sample reply per question'). It also notes the run filter and the as_of mode, so the selection conditions are explicit rather than inferred.

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.