Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

congress_summaries_search

Read-onlyIdempotent

Search Congressional Research Service summaries across all bills and congresses. Filter by congress, bill type, or update date to find relevant bill summaries.

Instructions

Search bill summaries across all bills and congresses. Unlike congress_bill_summaries (which requires a specific bill), this searches CRS summaries across the entire collection. Filter by congress, bill type, and date range. Sorted by last update date. Results include the associated bill reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: updateDate+asc or updateDate+desc
limitNoMax results (default: 20)
congressNoCongress number to filter by (omit for all congresses)
bill_typeNoBill type to filter by
toDateTimeNoFilter by update date to. Format: YYYY-MM-DDT00:00:00Z
fromDateTimeNoFilter by update date from. Format: YYYY-MM-DDT00:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.9.14
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "updateDate+asc",
+  "updateDate+desc"
+]
  2. Changed1 schema field changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2026.3.9

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context beyond that: results are sorted by last update date Ajithudf and include the associated bill reference, which helps the agent anticipate the output shape. No contradiction with annotations.

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?

Three sentences, no filler. The core purpose is front-loaded, the differentiation from the sibling appears in the second sentence, and filters/sort/output are listed compactly. Every sentence earns its place.

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?

For a search tool with 6 optional parameters and no output schema, the description covers all essential operational details: what it searches, scope, key filters, sort order, and the output's bill reference. The schema documents parameter specifics, so nothing critical is missing for an agent to invoke it correctly.

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 baseline is 3. The description mentions filtering by congress, bill type, and date range, but these map directly to the existing parameter descriptions without adding new meaning. It does not introduce any additional semantics beyond the 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 states a specific verb ('Search') and resource ('bill summaries'), and explicitly defines scope: 'across all bills and congresses'. It differentiates from the sibling congress_bill_summaries by calling out that it doesn't require a specific bill, so an agent can immediately distinguish this from the more targeted tool.

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

Usage Guidelines5/5

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

The description explicitly names the alternative (congress_bill_summaries) and the condition that selects between them ('which requires a specific bill' vs 'searches across the entire collection'). It also lists the key filters (congress, bill type, date range) and the sort order, giving clear guidance on when to use this tool.

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

Deploy Server

Other Tools