Skip to main content
Glama

get_bill_actions

Retrieves a bill's chronological congressional actions, newest first, from Congress.gov using a bill ID or Congress, bill type, and number; set a limit to control results.

Instructions

Chronological actions (newest first) for a specific bill from Congress.gov. Identify via billId or congress+type+number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bill_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNoMax actions to return (default 50, max 250).
billIdNo
numberNo
congressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the useful ordering trait (newest first) and the data source (Congress.gov). However, it omits auth requirements, rate limits, pagination behavior, error cases, and what an 'action' record contains.

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 short sentences, front-loaded with the resource and ordering, then the identification method. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter retrieval tool with 0% required parameters, no annotations, and no output schema, the description is thin. It does not explain the shape of returned actions, how the limit interacts with newest-first ordering, or what happens with ambiguous identifiers.

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 only 20%, so the description must compensate. It usefully explains the two identification paths (billId or congress+type+number), adding meaning beyond the bare schema for four parameters, but it does not clarify valid values for 'type' or whether billId overrides the combination.

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 states a specific resource (bill actions) and scope (a specific bill from Congress.gov) with ordering (chronological, newest first). It is clear what the tool retrieves, though it does not explicitly contrast with siblings like get_bill_details or get_bill_text.

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

Usage Guidelines2/5

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

The description explains how to identify the bill but gives no when-to-use guidance relative to alternatives, no exclusion conditions, and no prerequisites. An agent must infer that this is the tool for action history rather than bill metadata or text.

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