Skip to main content
Glama

Run a poll once now

run_poll_now
Destructive

Queue one run of a poll now, whatever its schedule. It asks every wording, or with share=true the next part of the poll's rotation at its sample_percent, exactly as a scheduled run would. It spends the account's balance, so the request must carry max_cost_usd (estimate_poll's run_now.hold_micro). Follow it with get_live_run, then read get_results once it settles. Refused with 409 if a run is already in progress. (POST /api/v1/polls/{id}/run)

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

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
shareNotrue: ask the next part of the rotation at the poll's sample_percent, as a scheduled run would (estimate_poll's per_run). false: every wording (run_now).
max_cost_usdNoThe most, in US dollars, you agree this may commit. Required: the call is refused with the amount it needs if this is missing or too low.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it spends the account's balance, requires a cost cap or the call is refused with the needed amount, and is refused with 409 if a run is already in progress. These cost and concurrency behaviors are not derivable from the destructive/openWorld/idempotent hints alone. It stops short of stating the double-queue consequence of retrying a non-idempotent call, but the coverage is strong.

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 with the action, then behavior (cost, rotation), then the follow-up workflow, then the failure mode — a logical order with no filler. The parenthetical references to estimate_poll's run_now.hold_micro and the endpoint are compact and purposeful, though the paragraph is dense.

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 money-spending, non-idempotent mutation with no output schema and three fully-documented params, the description covers cost commitment, conflict behavior, rotation semantics, and the read path afterward. An agent has everything needed to call it correctly and follow up.

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 the schema already documents id/slug, share's rotation semantics, and max_cost_usd's role. The description restates the share=true/false behavior and the max_cost_usd requirement, adding little meaning beyond the field descriptions. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Opens with a specific verb+resource+scope: "Queue one run of a poll now, whatever its schedule." This immediately distinguishes it from the scheduling siblings (start_poll/pause_poll) by making clear it forces a single immediate execution regardless of the existing schedule, and the trailing POST endpoint confirms the resource.

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?

Gives explicit workflow guidance: source max_cost_usd from estimate_poll's run_now.hold_micro, then follow with get_live_run and finally get_results once it settles. It also explains the share=true vs share=false selection. It does not explicitly contrast with start_poll (when to schedule recurring vs run once), leaving a small gap, but the operative guidance is clear.

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.