SiteCheck

Congress

congress

Read-only

US federal bills from Congress.gov (Library of Congress). Keyword search (q) runs over the 250 most recently updated bills of a Congress, since the API has no full-text search; each match gets its sponsor, status and latest action. A bill number (bill=hr1234-119) returns its cosponsor count, committees and up to 30 actions. Public domain. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Input Schema

Name	Required	Description
`q`	No	Words that must all appear in the bill title
`bill`	No	A bill, e.g. hr1234-119 or s50-119 (type, number, Congress)
`limit`	No	Max bills for q, 1-25, default 10
`congress`	No	Congress number 93 to the current one (119), default current

Output Schema

Name	Required	Description	Default
`note`	No
`query`	No
`total`	No
`source`	No
`results`	No
`scanned`	No
`returned`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {},
+    "note": {},
+    "query": {},
+    "results": {},
+    "returned": {},
+    "scanned": {},
+    "source": {},
+    "total": {}
+  },
+  "type": "object"
+}

AddedOct 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description goes well beyond them: it discloses the paid pricing model ($0.002 USDC per successful call via x402 on Base, Solana or Arc), that failed calls are not charged, and the coverage limitation of the search (only the 250 most recently updated bills). That is exactly the behavioral context an agent needs before invoking a metered tool.

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?

Four tight sentences, front-loaded with source and purpose, then mode behavior, then pricing. Every sentence carries information the agent needs; nothing is redundant with the schema or annotations.

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

Completeness5/5

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

Complete for a 4-parameter, zero-required tool with an output schema. Data source, both invocation modes, search limitations, result contents and billing behavior are all covered, so nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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 adds real semantics on top: it constrains what q actually searches (bill titles, only the 250 most recently updated bills), gives a concrete bill identifier format, and notes that a bill lookup returns cosponsor count, committees and up to 30 actions.

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 and resource ('US federal bills from Congress.gov') and clearly delineates its two operating modes: keyword search via q and direct bill-number lookup via bill. An agent can immediately tell what this tool returns in each mode, with no overlap ambiguity against siblings.

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?

Explains when each mode applies (q for keyword search, bill=hr1234-119 for a specific bill) and gives the key constraint that the API has no full-text search, so q only scans the 250 most recently updated bills. No explicit alternatives or exclusions are named, but the mode selection is unambiguous.

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

All SiteCheck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.