Skip to main content
Glama

search_votes

Read-onlyIdempotent

Find popular votes by title keyword and return Basel-Stadt results, with an optional limit for the number of matches.

Instructions

Search popular votes by title keyword (Basel-Stadt results)

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": {
      "query": "<query>"
    },
    "name": "search_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
queryYesTitle keyword, e.g. CO2, AHV

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default: 5, max: 20)."New value: +"max 20"
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword to find in vote titles (German/French/Italian)"New value: +"Title keyword, e.g. CO2, AHV"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered and the description only needs to add scope. It does add one genuinely useful behavioral fact — results are 'Basel-Stadt results' — but that phrase is ambiguous: it is unclear whether the corpus is limited to Basel-Stadt ballots or whether only cantonal result data is attached to national votes. No ordering, matching breadth (substring vs exact), or empty-result behavior is 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?

A single short sentence with the resource and search mode front-loaded; nothing is padded. The parenthetical scope note is compact but its placement at the end makes it read as an aside rather than a constraint, which slightly undercuts the structure.

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?

With no output schema and only two parameters, the description is close to sufficient, and annotations carry the read-safety story. However, for a search tool the agent still lacks any indication of what a hit contains or how the Basel-Stadt scoping constrains results, which matters for deciding whether to call this or get_voting_results.

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%, so both query (with examples 'CO2, AHV') and limit ('max 20', default 5) are already documented in the schema. The description only echoes the keyword idea and adds no matching semantics such as case sensitivity or multi-word handling, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search popular votes') plus the matching mechanism ('by title keyword'), so the agent knows exactly what it retrieves. It does not distinguish itself from the adjacent sibling tools get_voting_results and get_vote_details, leaving the agent to infer that this one is the keyword-search path rather than the fetch-by-id or results path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the presence of a keyword parameter signals 'use when you have a title keyword'. There is no explicit statement about when to prefer this over get_voting_results or get_vote_details, nor any note about what to do when a keyword search returns nothing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools