Skip to main content
Glama

Start a poll

start_poll
Destructive

Start a draft or paused poll on its schedule. Each run spends the account's balance, so the request must carry max_cost_usd, the most it may commit (estimate_poll gives the figure, and a refusal says the exact amount). Refused with 402 if the balance cannot cover it and 409 if this key's monthly allowance cannot; nothing is spent by a refusal. Confirm the cost with the account holder first. (POST /api/v1/polls/{id}/start)

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

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
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.6/5.0
Behavior5/5

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

Goes well beyond the destructive/non-idempotent annotations by disclosing the billing consequence of each run, the 402 and 409 failure semantics, and the important fact that a refusal spends nothing. These are exactly the traits an agent needs before committing money.

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-loads the action, then the cost requirement, then the error behavior, with no filler. The parenthetical path at the end is useful but the cost sentence is dense enough to need a second read.

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 two-parameter mutation with annotations already covering safety, the description supplies the money-spending model, error codes, refusal semantics, and the human-confirmation prerequisite. There is no output schema to explain, and nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: max_cost_usd is a commitment ceiling, estimate_poll supplies the number, and a refusal reports the exact amount required. This ties the parameter to the adjacent estimation tool rather than merely restating 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?

Specific verb + resource + precondition: 'Start a draft or paused poll on its schedule.' The 'on its schedule' qualifier implicitly separates it from run_poll_now, and the draft/paused restriction tells an agent exactly which poll states this applies to.

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?

Clear context for use: only draft or paused polls, obtain the figure from estimate_poll, and confirm the cost with the account holder before calling. It does not explicitly name run_poll_now as the alternative for an immediate run, so the routing guidance stops just short of complete.

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.