Skip to main content
Glama
loomiomcp
by soil-dev

get_poll

Read-onlyIdempotent

Retrieve full details for a single poll by numeric ID or short key, including options, current outcome, your stance, and whether results are visible.

Instructions

One poll by numeric id or short key: 1 call. Returns poll (full details, topic_id), poll_options[], current_outcome, my_stance, url; votes as items: list_thread_items with its topic_id. Results gate: results_visible / results_hidden_reason say whether tallies are present; absent counts mean HIDDEN, never zero.

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_or_key": "<id_or_key>"
    },
    "name": "get_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_keyYesPoll id or short key.
strip_htmlNoPlain text instead of HTML; default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / id_or_key / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[A-Za-z0-9_-]+$",
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z0-9_-]{1,128}$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
  2. Addedv0.0.13
  3. Removedv0.0.10
  4. First observedv0.0.6

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds non-obvious domain behavior on top: the results gate (`results_visible` / `results_hidden_reason`) and the warning that absent counts mean HIDDEN rather than zero. That last point prevents a real misinterpretation. Auth requirements, rate limits, and pagination are not mentioned, keeping it below the top mark.

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?

Front-loaded and information-dense with no filler sentences; every clause carries content (return shape, votes routing, results gating). It is somewhat telegraphic — the 'votes as items:' fragment is terse enough to require a second read — which keeps it from a 5.

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?

There is no output schema, so the description has to carry the return contract, and it does: it names `poll`, `poll_options[]`, `current_outcome`, `my_stance`, `url`, and the results-visibility fields, plus where to fetch votes. For a 2-parameter read tool this is essentially complete.

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 coverage is 100%, so both parameters are already documented, and the description's 'numeric id or short key' merely restates the schema's anyOf without adding format or lookup semantics. Baseline 3 applies; no added value beyond 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?

States a specific verb and resource ('One poll by numeric id or short key') and precisely scopes the result to a single entity, which cleanly separates it from list_polls and from the mutating update_poll/delete_poll siblings. The '1 call' note signals it is a single-fetch operation rather than a search.

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?

Usage context is mostly implied by the name and the '1 call' framing; there is no explicit 'use list_polls to find an id' or 'use update_poll to modify' guidance. It does route one sub-resource appropriately — votes are obtained via list_thread_items with the returned `topic_id` — which is a genuine alternative pointer, but it only covers part of the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.