Skip to main content
Glama

MeetingPoll — Fast Group Scheduling & Availability Polls

check_poll_status

Inspect a poll by ID or vanity slug to view poll mode, candidate schedule, response counts, and active state

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

Input Schema

NameRequiredDescriptionDefault
poll_idYesPoll ID or vanity slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; "inspect" and "view" correctly signal a non-mutating read, and the return contents are disclosed, which compensates for the absent output schema. However, nothing is said about error behavior for an unknown ID/slug, permissions or visibility requirements, or whether a slug lookup is case-sensitive.

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?

One front-loaded sentence with no filler; the output enumeration is efficient. Minor room to improve by separating the identifier note from the returned-field list for easier scanning.

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 simple one-parameter read tool with no output schema, the description covers both what it accepts and what it returns, which is the main completeness risk here. Remaining gaps (auth, not-found behavior) are modest against this complexity level.

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% and the single parameter's description already states "Poll ID or vanity slug"; the description repeats that phrasing without adding format, validation, or ambiguity-resolution detail. Baseline 3 is appropriate when the schema does the work.

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?

"Inspect a poll by ID or vanity slug" gives a specific verb and resource, and the enumerated outputs (poll mode, candidate schedule, response counts, active state) make the scope concrete. It does not explicitly distinguish itself from siblings like get_poll_consensus, but the read-only status framing is distinct enough for an agent to select it.

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 listed return fields imply the usage context—fetching current poll configuration and state—but there is no explicit when-to-use statement, no exclusion of alternatives such as get_poll_consensus, and no prerequisites mentioned. Guidance is inferable rather than stated.

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.

Resources