Skip to main content
Glama

Check a projection

check_projection
Read-onlyIdempotent

Returns the projection's state: working; waiting, with the question the user must answer; done, with each person's projected share of the vote in whole percents and fovub's warning; or failed, with the reason. With wait_seconds, it waits up to that many seconds for the projection to ask a question or finish. Needs the user's fovub sign-in.

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": {
      "run_id": "<run_id>"
    },
    "name": "check_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id that start_projection returned.
languageNoThe user's language as a BCP 47 code, such as es, es-MX, or fr: the language of the user's Claude account, or the language the user writes in. fovub then gives the questions, their choices, and the result's warning in that language. Leave it out for English.
wait_secondsNoWait up to this many seconds, at most 50, for a question or the result. Use 45 while it works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "The user's language as a BCP 47 code, such as es, es-MX, or fr: the language of the user's Claude account, or the language the user writes in. fovub then gives the questions, their choices, and the result's warning in that language. Leave it out for English.",
      +  "maxLength": 35,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: it blocks for up to wait_seconds rather than returning immediately, it requires the user's fovub sign-in, and it discloses what each terminal state carries (shares in whole percents, a warning, a failure reason). It does not say what happens if the wait expires without a question, but the rest of the blocking/latency behavior is well disclosed.

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?

The return states are front-loaded in the first sentence, with the blocking behavior and auth requirement following. The state enumeration is dense but each clause carries information an agent needs to branch on. Minor cost: the sentence runs long and could be split for scanability.

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

Completeness4/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 must describe returns — and it does, covering all four states and the payload of each. With annotations handling safety and the schema handling parameters, the remaining gap is small: no guidance on what to do after "working" or after a wait expires, and no sense of typical latency.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description restates the wait_seconds semantics and the language localization effect without adding syntax, defaults or edge cases beyond what the schema says. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ("Returns the projection's state") and enumerates the exact state values an agent will encounter — working, waiting, done, failed — plus what accompanies each. This is enough to distinguish it from start_projection (which begins a run) and answer_question (which supplies the user's answer) 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 clear operating context: use wait_seconds to block until a question appears or the run finishes, which tells the agent this is a polling tool. It also flags the sign-in prerequisite. It stops short of explicitly routing the agent — e.g. that a "waiting" result means you should call answer_question — so the alternative is only implied rather than named.

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.

Resources