Skip to main content
Glama

Get a poll

get_poll
Read-onlyIdempotent

A poll's settings and every version: the questions and their wordings exactly as asked, the models, samples and search depth, plus any prediction markets associated with it. Accepts the poll's id or its public address (slug). (GET /api/v1/polls/{id})

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_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description adds genuine context by disclosing that the response covers *every version* of the poll along with models, samples, search depth, and prediction markets, which signals a potentially large composite payload. It stops short of saying what happens for an unknown id/slug or whether versions are paginated.

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?

Two information-dense sentences plus the API route, with the payload contents front-loaded before the identifier note. Nothing is redundant, though the parenthetical endpoint path is of marginal value to an agent and the first sentence packs many items into one clause chain.

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?

For a single-parameter read tool with no output schema, the description carries the necessary burden by enumerating what the response contains. Only minor gaps remain: error behavior for a missing poll and any indication of response size or version ordering.

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 schema field description ('The poll's id, or its public address (slug)') is essentially identical to the sentence in the tool description. The description therefore adds no meaning beyond the schema, so the baseline of 3 applies.

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 uses a specific verb (retrieves a poll) and enumerates the resource's contents: settings, every version's questions and exact wordings, models, samples, search depth, and associated prediction markets. This clearly distinguishes it from list_polls, get_results, and create_poll without the agent needing to inspect any schema.

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 a single-record lookup keyed by id or slug, and notes the dual identifier form, which helps the agent know it can call this directly with either. However, it never states when to prefer this over get_results or list_polls (e.g., to discover an id or to view definitions rather than outcomes), leaving that routing to inference.

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.