Skip to main content
Glama
adathouse
by adathouse

Search bill actions

search_actions

Search legislative action history to find events like 'Passed House' or 'Became Public Law' by text, type, or date. Each result includes the related bill.

Instructions

Search the legislative action history across bills. Use this to find events like 'Passed House', 'Passed Senate', 'Became Public Law', or to inspect actions by type/code. Each result includes the related bill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textContainsNoSubstring to match within the action text, e.g. 'Passed House', 'Became Public Law', 'Signed by President'.
actionTypeNoExact action type, e.g. 'Floor', 'BecameLaw', 'IntroReferral'.
actionCodeNoExact action code.
actionDateAfterNoOnly actions on/after this date (YYYY-MM-DD).
actionDateBeforeNoOnly actions on/before this date (YYYY-MM-DD).
sortByNoField to sort by. Default: actionDate.
sortOrderNoSort direction. Default: DESC (newest first).
limitNoMax results to return (1-50). Default 10.
afterNoRelay pagination cursor. Pass the `pageInfo.endCursor` from a previous result to fetch the next page.
Behavior3/5

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

No annotations provided; description discloses that results include related bill but does not explicitly state read-only nature or other behavioral traits like rate limits.

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 sentences front-loaded with purpose, efficient and no wasted words.

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?

Covers main use cases but omits pagination explanation and default sort order; no output schema requires more detail on return values.

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% with good descriptions; description adds value via examples but does not detail all parameters beyond schema.

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?

The description clearly states the tool searches legislative action history across bills, uses specific verb 'Search', and distinguishes from siblings like search_bills by focusing on actions.

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

Usage Guidelines4/5

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

Provides concrete examples of when to use (e.g., find 'Passed House'), but lacks explicit comparison to alternatives or when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adathouse/cdgmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server