Skip to main content
Glama

Pause a poll

pause_poll
Idempotent

Pause an active poll: no further runs start until it is started again. A run already in progress finishes. Needs only the write scope, since pausing stops spending. (POST /api/v1/polls/{id}/pause)

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": "pause_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

A4.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: pausing is forward-only (no new runs start, an in-progress run completes) and requires only the write scope because it stops spending. Those are operational facts the annotations (idempotent, non-destructive) do not convey. Minor gap: nothing about what the response contains or whether pausing an already-paused poll errors, though idempotentHint covers retry safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the effect and followed by the in-flight run caveat, the scope requirement, and the endpoint. Every sentence earns its place.

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?

For a single-parameter mutation with no output schema, this covers effect, edge case (in-progress run), permission scope, and endpoint. An agent has everything needed to call it 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 coverage is 100% and the single 'id' parameter already documents that it accepts an id or public slug. The description adds no additional meaning about the identifier, so it sits at the baseline where the schema does the work.

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 ('Pause an active poll') and immediately defines the operational meaning: no further runs start until it is started again. This distinguishes it from start_poll/run_poll_now by the state transition it performs, without needing to open a schema.

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?

The description makes clear it applies to an active poll and that resumption happens via starting again, which signals when to reach for it versus start_poll or run_poll_now. It does not explicitly name an alternative or state a when-not case, so it stops short of full routing guidance.

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.