Skip to main content
Glama

Update a poll

update_poll
Idempotent

Replace a poll's definition with a new one. Before its first run the version is edited in place; once a version has run it is locked and a new version is made, so results always say what was asked. Send the whole definition, as create_poll takes it. (PUT /api/v1/polls/{id})

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>",
      "title": "<title>",
      "schedule": "<schedule>",
      "samples_per_cell": "<samples_per_cell>",
      "questions": "<questions>",
      "panel": "<panel>"
    },
    "name": "update_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
panelYes1 to 30 models to ask, each once.
titleYesThe poll's title.
deliveryNorealtime (the default), or batch: scheduled runs ask the models that can be batched (Anthropic) through the providers' batch APIs, cheaper, with answers arriving up to 2 hours after the run starts; run_poll_now is always real time. OpenAI and Google models are asked at their flex tier, the same price, in real time, either way. Left out: unchanged.
end_dateNoThe last day it runs, at most 90 days after start_date.
run_timeNoThe time of day it runs, HH:MM in time_zone; null runs from the moment it is started.
scheduleYesonce, daily or weekly.
questionsYes1 to 50 questions, in order.
time_zoneNoThe IANA time zone of its dates and run time.America/Anchorage
index_nameNoA name for the composite of the poll's Better-Worse index questions, such as "AI Economy Index"; empty for "Composite Better-Worse index". Shown only when two or more questions have the index.
start_dateNoThe first day it runs, YYYY-MM-DD in time_zone; needs run_time.
change_noteNoWhy this version differs from the last, kept in the poll's history.
descriptionNoWhat the poll is for, or empty.
run_weekdayNoWeekly polls: the day it runs, 0 = Sunday.
search_depthNoSearches allowed per answer, for every model with search on.
restored_fromNoThe earlier version this one was started from, or null.
system_promptNoThe system prompt every wording is asked under unless it has its own; empty for none.
sample_percentNoThe share of the poll's wordings each scheduled run asks, 1 to 100 percent; every wording is asked once before any is asked again. Left out: unchanged (100 for a new poll). run_poll_now asks this share with share=true, every wording otherwise.
samples_per_cellYesHow many times each model is asked each wording per run, 1 to 50: more samples, narrower ranges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only give the safety profile (readOnly=false, destructive=false, idempotent=true); the description adds the genuinely important behavior: in-place editing before the first run, lock-and-fork afterwards so historical results stay interpretable. That is a mutation side effect an agent could not infer from structured fields, and it is consistent with the idempotentHint (PUT semantics).

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?

Four short sentences, front-loaded with the action, then the behavioral consequence, then the payload rule, then the transport hint. No filler; the parenthetical endpoint is the only marginal element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter mutation the versioning contract is well covered, and the schema fully documents the parameters. However, there is no output schema and the description never says what an update returns (the edited poll vs. a new version id) or what happens to an in-flight run, leaving a real gap for a versioned write.

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 100% across 19 parameters, so the schema does the heavy lifting and 3 is the baseline. The description still adds meaning by stating the whole definition must be sent and that its shape mirrors create_poll's input, which resolves whether omitted fields are patched or blanked.

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 concrete verb and resource ("Replace a poll's definition with a new one") and immediately scopes it against create_poll by saying the payload is the same shape. The versioning sentence clarifies it is a full-definition replacement rather than an incremental patch, so an agent can tell it apart from pause_poll/run_poll_now without opening 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?

"Send the whole definition" is an explicit usage constraint on how to call it, and the note that pre-run versions are edited in place while run versions are locked tells the agent the consequence of calling it late in a poll's life. It stops short of naming an alternative (e.g. create_poll for a brand-new poll) or stating exclusions, so it is clear context without explicit routing.

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.