Skip to main content
Glama

get_bill_history

Read-only

Retrieve a bill's legislative action history—committee referrals, readings, vote tallies, governor actions, and floor debate dates—with options to page results or return the full timeline.

Instructions

Action history of a bill (committee referrals, readings, votes with tallies as yeas-nays-absent, governor action) plus floor debate dates. By default returns the last 10 actions plus every vote action, oldest first.

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": {
      "bill": "<bill>"
    },
    "name": "get_bill_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
limitNoMax items to return (1-50).
offsetNoStart position for paging; use next_offset from a prior call.
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.
full_historyNoReturn every action (paged) instead of recent + votes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and does add value: it discloses the default truncation rule (last 10 actions plus all vote actions), the ordering ('oldest first'), and the vote tally format. It does not mention rate limits, truncation via max_chars, or what happens when a bill is not found, which keeps it from a 5.

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?

Two dense sentences, front-loaded with the resource and its contents, then the default behavior. Every clause carries information (content types, tally format, ordering, default rule) with no filler or restatement of the name.

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 six-parameter read-only tool with no output schema, the description covers the important unknowns: what is returned, in what order, and how the default differs from full_history. It leaves the interaction between limit/offset and the 'last 10 + all votes' default unexplained, and says nothing about max_chars truncation, which is a minor remaining 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 bill, limit, offset, session, max_chars, and full_history. The description adds only a little: it clarifies the semantic effect of full_history ('instead of recent + votes') and explains why the default result differs from the default limit of 25. That is marginal added meaning over the schema, so the 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?

The description names a specific verb+resource ('Action history of a bill') and enumerates exactly what is included: committee referrals, readings, votes with yeas-nays-absent tallies, governor action, and floor debate dates. It does not explicitly differentiate itself from siblings like get_bill or get_bill_documents, so it stops short of a 5.

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 implied rather than stated: the default behavior ('last 10 actions plus every vote action') tells an agent what it gets without asking, but there is no explicit guidance on when to prefer full_history, when to reach for get_bill instead, or when to page with offset. An agent can infer the use case but is given no alternatives or exclusions.

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