get_vote_recordGet details about a specific House roll call vote including all member positions. Note: only House votes are available via this tool.
| Name | Required | Description | Default |
|---|---|---|---|
| session | No | Session number, default current | |
| congress | No | Congress number, default 119 | |
| rollCallNumber | Yes | Roll call number |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The tool's read-only nature is implied by 'Get details' and is consistent with the readOnlyHint annotation. The description adds transparency by specifying that it covers 'all member positions' and that only House votes are available, which goes beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, consisting of two short sentences. The first sentence conveys the core purpose, and the second provides a critical constraint. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the fully described input schema and annotations, the description covers the tool's primary purpose and a key constraint (House-only). It does not detail the output format, but no output schema exists, and the description does mention 'all member positions' as part of the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description does not add any parameter-specific guidance beyond what is already in the schema's property descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' and identifies the resource as 'House roll call vote including all member positions.' It clearly states the tool's scope, but does not explicitly differentiate it from sibling tools like 'get_voting_history'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes a note that 'only House votes are available via this tool,' which implies not to use it for Senate votes. However, it does not mention when to use this tool versus alternatives such as 'get_voting_history' or other analysis tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, specific purpose with detailed descriptions that differentiate them. Prefix patterns like get_district_, search_, analyze_, get_, etc., help an agent easily identify the correct tool for a task.
All tool names use a consistent verb_noun or verb_noun_noun pattern with underscores. The naming convention is uniform across the entire set, with no mixing of styles or ambiguous verbs.
With 47 tools, the count is high but justified by the broad scope of civic data analysis. While some agents might find the sheer number overwhelming, the tools are organized into clear categories (district profiles, searches, analyses) that make navigation feasible.
The toolset covers an impressively wide range of domains: legislation, representatives, districts, voting, committees, campaign finance, lobbying, federal spending, regulations, environment, energy, healthcare, housing, disaster, banking, consumer complaints, crime, vehicles, and more. There are no obvious missing operations for a civic data platform.