Skip to main content
Glama

Start a projection

start_projection
Destructive

Starts fovub's projection of the share of the vote between two people for one seat. It takes $1 from the user's fovub balance, and the money comes back if the projection fails. A projection runs for minutes and asks the user questions as it works; follow it with check_projection. 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": {
      "seat_id": "<seat_id>",
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "start_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoThe view that find_seat returned with the seat, for a seat from history or from a work of fiction. Leave it out for a real seat.
seat_idYesThe seat_id that find_seat returned.
person_aYesThe first person's full name.
person_bYesThe second person's full name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "The view that find_seat returned with the seat, for a seat from history or from a work of fiction. Leave it out for a real seat.",
      +  "enum": [
      +    "historical",
      +    "fiction"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the $1 charge, the refund condition if the projection fails, the multi-minute runtime, the interactive question flow, sign-in requirements, and the recommended follow-up tool. These details substantially enrich the agent's understanding of a non-read-only, potentially destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tightly written sentences with no wasted wording. Cost/refund, runtime and interaction behavior, follow-up guidance, and authentication are all front-loaded and useful.

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?

For a paid, asynchronous, interactive start tool with no output schema, the description covers the important behavioral context an agent needs before calling it. It does not explain what start_projection returns or how check_projection is keyed to the started projection, leaving a small completeness gap.

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 the schema already documents seat_id, person_a, person_b, and the optional view parameter. The description adds no field-level meaning beyond the general 'two people for one seat' framing, so baseline 3 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?

The description states a specific verb and resource: starts a projection of the share of the vote between two people for one seat. It also names check_projection as the follow-up tool, which helps distinguish this action from reviewing a running projection.

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?

It gives clear operating context: the call costs $1, may take minutes, asks questions, requires sign-in, and should be followed with check_projection. It does not compare against alternatives such as buy_projection or state when not to use this tool, so it falls short of explicit when/when-not guidance.

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