Skip to main content
Glama

Get a poll's results

get_results
Read-onlyIdempotent

A poll's results. For choice and scale questions each answer's share per model per run, with its Wilson 95% interval; for number and scale questions each model's mean with its 95% interval. Every point carries available_at, when this reader could first have seen it. as_of reads the results exactly as they stood at a past moment (no later run and no later re-reading of an answer), and first_release=true reads every answer as first published; both need a free key (the historical reads are what a backtest pulls, and a key says who is pulling). Versions are continued onto the latest unless version is given. (GET /api/v1/polls/{id}/results)

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

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
viewNopooled adds up a question's wordings; by-wording keeps them apart.pooled
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. Needs a key.
versionNoOne version only. Default: every version continued onto the latest.
first_releaseNotrue: each answer's first reading, as first published, rather than its latest. Needs a key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world read, so the safety profile is covered. The description adds behavior annotations cannot: an authentication requirement for historical reads ("needs a key"), and the precise scoping semantics of as_of ("no later run and no later re-reading of an answer"). It does not mention response size, pagination, or error behavior for a missing poll, so it stops short of full disclosure.

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?

Every sentence carries information, but the structure is poor: it opens with a noun fragment ("A poll's results.") rather than a statement of action, then packs return shape, availability semantics, key requirements, and version defaults into dense run-on sentences with nested parentheticals. The most decision-relevant fact (this is a read endpoint with key-gated historical modes) is buried mid-paragraph.

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?

With no output schema, the description usefully explains the return shape (per-model per-run shares, intervals, available_at on every point), which an agent could not otherwise know. It also flags the key gate for historical reads. Minor gaps remain around pagination and result volume for large polls, but the definition is sufficient to call the tool correctly.

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%, so the schema already documents id, view, as_of, version, and first_release, including enum meanings for view. The description restates the same semantics in prose and adds the useful relationship that as_of and first_release both require a key, but contributes no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

The title supplies the verb ("Get") and the description supplies the resource and payload in detail: a poll's per-model, per-run answer shares with Wilson 95% intervals and means with 95% intervals. An agent knows exactly what comes back. What is missing is any differentiation from siblings like get_poll or get_live_run, so it is clear but not disambiguated.

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?

Strong conditional guidance for the optional parameters: as_of reads at a past moment, first_release reads answers as first published, both require a free key, and versions default to continued-onto-latest unless version is given. It even motivates the historical modes ("what a backtest pulls"). No guidance on when this is preferable to get_poll or get_live_run, which is the remaining gap.

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.