Skip to main content
Glama

Council votes on a business

get_parliament_votes
Read-only

Retrieve formal council votes for a parliamentary business by its short number, including the subject, what yes/no meant, and the yes/no/abstain tallies.

Instructions

Formal council votes for a parliamentary business (by short number like '23.4567'), including the subject, what yes/no meant, and the actual yes/no/abstain tallies of the most recent vote.

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": {
      "business_short_number": "<business_short_number>"
    },
    "name": "get_parliament_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax votes to list
business_short_numberYesBusiness short number, e.g. '23.4567' (from search_parliament_business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds real context about what comes back: the subject, an explanation of what yes/no meant, and the actual tallies. The one gap is a mild tension between 'the most recent vote' (singular) and the limit parameter that lists up to 10 votes, leaving result ordering and multi-vote behavior slightly fuzzy.

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 front-loaded sentence that identifies the resource first, then the key format, then the payload. Slightly dense and the repeated example number duplicates the schema, but no sentence is wasted.

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 carry return-value explanation, and it does name the main returned elements for this otherwise simple two-parameter read tool. It stops short of describing ordering or what happens when a business has no recorded votes, which keeps it from a 5.

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 parameters are already documented, including the short-number pattern and the limit bounds. The description repeats the example number but adds nothing about the limit parameter or what a larger limit yields, so it neither helps nor hurts beyond the schema baseline.

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 (formal council votes for a parliamentary business) plus the lookup key format ('23.4567'), and lists the payload (subject, meaning of yes/no, tallies). That return-content detail distinguishes it from a business-details sibling such as get_parliament_business without needing to name it.

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 short-number key and the schema note that it comes 'from search_parliament_business' sketch a workflow, but the description itself never says when to call this versus get_parliament_business or the local-parliament equivalents, and gives no exclusions.

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