Skip to main content
Glama

BRAINIAC Bills & eCFR Section Lookup

Look up US Congress bill status (119th)

legislative-intelligence_congress-bill-status
Read-onlyIdempotent

Return status, titles, sponsor, committees, latest action and public law for a bill or resolution of the 119th Congress from the vendored GPO BILLSTATUS extract. Price $0.03 USDC. POST /api/v1/legislative-intelligence/congress-bill-status. An unpaid call returns the x402 payment terms and does not run.

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": {
      "congress": "<congress>"
    },
    "name": "legislative-intelligence_congress-bill-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 50. Required.
queryNoquery, string, length 3 to 200. Optional.
numberNonumber, integer, from 1 to 9007199254740991. Optional.
billTypeNobillType, string, one of hr, s, hjres, sjres, hres, sres. Optional.
congressYescongress, integer, from -9007199254740991 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
billNobill. Object.
foundNofound. Boolean.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds the non-obvious parts an agent must know before calling: a $0.03 USDC charge, the x402 payment-terms response for unpaid calls, and the fact that an unpaid call does not execute. That billing/auth behavior is the highest-value disclosure here and is not present in structured fields.

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?

Three sentences, front-loaded with what is returned, then transport and pricing. The endpoint path and price are packed into the same breath as the payload description, but nothing is redundant or padded.

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?

Output schema exists, so enumerating return fields is a bonus rather than a requirement, and the payment flow is fully disclosed. What remains thin is lookup-mode guidance across the five parameters, which matters for a tool accepting both a keyword query and a structured bill number.

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% and each parameter carries its own description and enum, so the schema does the heavy lifting. The description reinforces that the target is a bill or resolution but does not explain how query differs from number+billType, which is the one semantic gap the schema does not close.

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 (return) with an explicit field list (status, titles, sponsor, committees, latest action, public law) scoped to bills/resolutions of the 119th Congress from a named vendored GPO BILLSTATUS extract. That scope clause is what separates it from the UK Parliament and eCFR siblings without needing to name them.

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?

The scope sentence implies when it applies (119th Congress bills only), but there is no explicit when-not guidance and no routing to the sibling tools for other jurisdictions or for statute text. The choice between the query, number and billType lookup paths is left entirely implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources