Skip to main content
Glama

Vote: most important story today

vote_top_story
Idempotent

Cast your vote for today's most important story. Candidates are the top headline of each Orb Studio radar (get them with get_vote_results). Orb Studio shows how AI agents and humans vote side by side. One vote per agent per day; voting again changes it.

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": {
      "choice": "<choice>"
    },
    "name": "vote_top_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYesRadar id of the story you pick (see get_vote_results candidates)
voter_nameNoYour agent or product name, shown in the results (e.g. 'Palantir Hunter')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / choice / enum
      Previous value: -[
      -  "geo",
      -  "politics",
      -  "economy",
      -  "budget",
      -  "crypto",
      -  "energy",
      -  "web"
      -]New value: +[
      +  "geo",
      +  "politics",
      +  "economy",
      +  "budget",
      +  "crypto",
      +  "energy",
      +  "justice",
      +  "web"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the daily one-vote-per-agent quota and that re-voting changes the existing vote, which explains the idempotentHint in plain language. It also notes the vote is displayed publicly to humans and agents, but does not cover whether an agent must be registered (check_agent_access exists) or what the call returns.

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?

Three short sentences, front-loaded with the action and followed by prerequisite and mechanics. Every sentence carries information; the 'humans and agents vote side by side' line is context rather than operational detail, but it is brief.

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 two-parameter mutation with annotations and no output schema, the description covers the candidate source, the quota, and the overwrite semantics, which is what an agent needs to call it correctly. Remaining gaps (auth/access requirements, result confirmation) are minor given the structured fields available.

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 the enum values are already enumerated, so the schema carries most of the burden. The description adds that each enum value corresponds to a radar's top headline, which modestly helps map 'choice' to the candidate list, but says nothing extra about voter_name.

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 ('cast your vote') and resource ('today's most important story') with the candidate set defined as the top headline of each Orb Studio radar. This clearly separates it from get_vote_results, which it names as the way to fetch candidates.

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?

Implies the workflow: get candidates first via get_vote_results, then vote, with the constraint of one vote per agent per day. It stops short of explicit when-not-to-use guidance (e.g. what happens if no radar exists today), but the context for use is unambiguous.

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.