Skip to main content
Glama

Estimate a poll's cost

estimate_poll
Read-onlyIdempotent

What a poll will cost, from the same prices the worker charges by: one run's typical and 95th-percentile charge, what a run holds from the balance while it runs, and what starting the poll commits (hold per run times the runs left before its end date, or a month of runs when it has none). Show this to the account holder before start_poll or run_poll_now. (GET /api/v1/polls/{id}/estimate)

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": "estimate_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.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's job is to add semantics, and it does: it explains that prices come from the worker's actual rates, what the hold represents (balance reserved during a run), and how the start commitment is computed (hold per run times remaining runs, or a month of runs when there is no end date). It does not cover auth requirements, rate limits, or staleness of the estimate, which keeps it from a 5.

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 core purpose and sized to what an agent needs, with no filler sentences. The structure suffers slightly from a long run-on clause with nested parentheses around the commitment calculation, which makes it harder to parse at a glance than a short bulleted breakdown would be.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so by naming the four cost components an agent will receive. Combined with the endpoint path and the sequencing instruction, an agent has enough to call this correctly and interpret the result.

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 there is a single parameter, whose schema description already tells the agent it accepts a poll id or its public slug. The description adds nothing about the identifier, only about the returned numbers, so the baseline 3 for fully documented parameters is appropriate.

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 combination ("What a poll will cost") and then enumerates exactly what the estimate contains: typical and 95th-percentile charge, the running hold, and the start commitment. This is clearly a cost-estimate read on a poll, distinguishable from get_poll or start_poll without opening any 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?

Gives an explicit trigger and named siblings: "Show this to the account holder before start_poll or run_poll_now." That is a concrete when-to-use condition tied to two alternatives. It stops short of a 5 because there is no when-not guidance (e.g. whether to call it when the poll is paused or already ended).

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.