Skip to main content
Glama

congressgov-mcp-server

Congress.gov Committee Lookup

congressgov_committee_lookup
Read-onlyIdempotent

Browse congressional committees and their legislation, reports, and nominations. Committee codes follow the pattern chamber-prefix (h/s/j) + abbreviation + 2-digit number — use 'list' (with optional 'filter' for name→code resolution) to discover codes, then 'get' or drill into 'bills', 'reports', or 'nominations' ('nominations' is Senate-only). 'get' and sub-resources only need committeeCode (chamber is inferred from the prefix); pass chamber explicitly to override. The 'bills' sub-resource defaults to 'recent' order (newest update-date first); pass order='oldest' for ascending update-date order. Upstream omits bill titles from the 'bills' sub-resource — rows carry only {congress, billType, billNumber, actionDate, relationshipType, url}; chain 'congressgov_bill_lookup get' per row to retrieve titles and policy area.

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page (1-250).
orderNoSort order for the 'bills' sub-resource. 'recent' (default) returns newest update-date first; 'oldest' returns ascending update-date order. Ignored by other operations.recent
filterNoFilter committee-list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'; fuzzy-matched rows are labeled approximate.
offsetNoPagination offset.
chamberNoChamber filter for 'list', or override for 'get' and sub-resources (otherwise inferred from committeeCode prefix).
congressNoCongress number.
operationYesWhich data to retrieve.
committeeCodeNoCommittee system code, e.g. 'hsju00'. Required for 'get' and sub-resources. Codes are letters + a 2-digit suffix and are matched case-insensitively. Any other non-blank value is treated as a committee name and resolved automatically — single-word names ('Judiciary') included — or use operation:'list' with filter to browse.

Output Schema

NameRequiredDescriptionDefault
dataNoResult rows. Per-tool item shape is rendered in the markdown body.
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when results are empty, a page is past the end, or a caveat applies.
committeeNoDynamic upstream JSON record.
paginationNoPagination metadata: total count and next offset.
totalCountNoTotal results across all pages.
effectiveQueryNoThe browse scope and applied filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: A process-local attempt budget or the shared upstream credential/IP quota was reached; upstream hourly limits vary and DEMO_KEY also has a daily quota. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). `upstream_timeout`: The Congress.gov request deadline expired or the upstream returned an HTTP timeout response. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: A process-local attempt budget or the shared upstream credential/IP quota was reached; upstream hourly limits vary and DEMO_KEY also has a daily quota. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `api_key_rejected`: The api.data.gov gateway rejected the server's configured CONGRESS_API_KEY (missing, invalid, disabled, unauthorized, or unverified); the gateway code is in data.upstreamCode. No change to the call's arguments can fix it. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status) or could not be reached, or the Senate LIS feed failed (5xx, a timeout, or a senate.gov HTTP 403 refusal, which carries retryable: false). `upstream_timeout`: A Congress.gov request or a congress.gov document fetch timed out or returned an HTTP timeout response, or the call's upstream requests could not finish inside its 50-second budget. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "not_found",
      -  "rate_limited",
      -  "invalid_request",
      -  "upstream_error",
      -  "upstream_timeout"
      -]New value: +[
      +  "not_found",
      +  "rate_limited",
      +  "invalid_request",
      +  "api_key_rejected",
      +  "upstream_error",
      +  "upstream_timeout"
      +]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: The Congress.gov API rate limit (5,000 requests/hour per key) was exceeded. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: A process-local attempt budget or the shared upstream credential/IP quota was reached; upstream hourly limits vary and DEMO_KEY also has a daily quota. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). `upstream_timeout`: The Congress.gov request deadline expired or the upstream returned an HTTP timeout response. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "not_found",
      -  "rate_limited",
      -  "invalid_request",
      -  "upstream_error"
      -]New value: +[
      +  "not_found",
      +  "rate_limited",
      +  "invalid_request",
      +  "upstream_error",
      +  "upstream_timeout"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"Filter committee list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'. Fetches the full chamber set and matches client-side; fuzzy-matched rows are labeled approximate."New value: +"Filter committee-list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'; fuzzy-matched rows are labeled approximate."
    • addedOutput schema / properties / committee
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Dynamic upstream JSON record.",
      +  "properties": {},
      +  "type": "object"
      +}
  4. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "effectiveQuery",
      +      "totalCount"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: A requested bill, member, committee, report, vote, or nomination does not exist in Congress.gov. `rate_limited`: The Congress.gov API rate limit (5,000 requests/hour per key) was exceeded. `invalid_request`: Congress.gov rejected the request as malformed — a bad date range or an identifier with an unexpected shape. `upstream_error`: Congress.gov returned an unexpected error (5xx or another non-2xx status). Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "not_found",
      +            "rate_limited",
      +            "invalid_request",
      +            "upstream_error"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "effectiveQuery",
      -  "totalCount"
      -]
  5. Changed2 schema fields changed
    • changedInput schema / properties / committeeCode / description
      Previous value: -"Committee system code, e.g. 'hsju00'. Required for 'get' and sub-resources. Codes are lowercase letters + 2-digit suffix. Pass a committee name here and the tool will attempt to resolve it automatically — or use operation:'list' with filter to browse."New value: +"Committee system code, e.g. 'hsju00'. Required for 'get' and sub-resources. Codes are letters + a 2-digit suffix and are matched case-insensitively. Any other non-blank value is treated as a committee name and resolved automatically — single-word names ('Judiciary') included — or use operation:'list' with filter to browse."
    • changedInput schema / properties / committeeCode / pattern
      Previous value: -"^([a-z]{2,6}\\d{2}|.*\\s.*)$"New value: +"\\S"
  6. Changed2 schema fields changed
    • changedInput schema / properties / committeeCode / description
      Previous value: -"Committee system code (e.g., 'hsju00'). Required for get and sub-resources."New value: +"Committee system code, e.g. 'hsju00'. Required for 'get' and sub-resources. Codes are lowercase letters + 2-digit suffix. Pass a committee name here and the tool will attempt to resolve it automatically — or use operation:'list' with filter to browse."
    • addedInput schema / properties / committeeCode / pattern
      Added value: +"^([a-z]{2,6}\\d{2}|.*\\s.*)$"
  7. Changed1 schema field changed
    • addedInput schema / properties / filter
      Added value: +{
      +  "description": "Filter committee list results by name (e.g., 'transportation', 'armed services'). Only meaningful for 'list'. Fetches the full chamber set and matches client-side; fuzzy-matched rows are labeled approximate.",
      +  "type": "string"
      +}
  8. Changed6 schema fields changed
    • removedOutput schema / description
      Removed value: -"Detail-mode key 'committee' carries: Committee record for `get` (name, chamber, subcommittees, history, sub-resource counts); absent for `list` and sub-resources."
    • addedOutput schema / properties / effectiveQuery
      Added value: +{
      +  "description": "The browse scope and applied filters.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when results are empty, a page is past the end, or a caveat applies.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / query
      Removed value: -{
      -  "description": "Echo of the applied filters for list-mode queries. Rendered as the first line of the response.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total results across all pages.",
      +  "type": "number"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "effectiveQuery",
      +  "totalCount"
      +]
  9. Changed4 schema fields changed
    • changedOutput schema / description
      Previous value: -"Committee data from Congress.gov API."New value: +"Detail-mode key 'committee' carries: Committee record for `get` (name, chamber, subcommittees, history, sub-resource counts); absent for `list` and sub-resources."
    • addedOutput schema / properties / data
      Added value: +{
      +  "description": "Result rows. Per-tool item shape is rendered in the markdown body.",
      +  "items": {
      +    "additionalProperties": {},
      +    "description": "Upstream JSON record. Per-tool item shape is rendered in the markdown body.",
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / pagination
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Pagination metadata: total count and next offset.",
      +  "properties": {
      +    "count": {
      +      "description": "Total result count across all pages.",
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "nextOffset": {
      +      "anyOf": [
      +        {
      +          "maximum": 9007199254740991,
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Offset to pass for the next page, or null when there are no more pages."
      +    }
      +  },
      +  "required": [
      +    "count"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "description": "Echo of the applied filters for list-mode queries. Rendered as the first line of the response.",
      +  "type": "string"
      +}
  10. Changed1 schema field changed
    • changedInput schema / properties / chamber / description
      Previous value: -"Chamber filter. Required for 'get' and sub-resources."New value: +"Chamber filter for 'list', or override for 'get' and sub-resources (otherwise inferred from committeeCode prefix)."
  11. Changed1 schema field changed
    • addedInput schema / properties / order
      Added value: +{
      +  "default": "recent",
      +  "description": "Sort order for the 'bills' sub-resource. 'recent' (default) returns newest update-date first; 'oldest' returns ascending update-date order. Ignored by other operations.",
      +  "enum": [
      +    "recent",
      +    "oldest"
      +  ],
      +  "type": "string"
      +}
  12. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as read-only, open-world, and idempotent, but the description adds important behavioral context: committeeCode inference rules, the Senate-only limitation on nominations, the default 'recent' order for bills, and the upstream omission of bill titles with row fields spelled out. This is meaningful disclosure beyond structured metadata.

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?

The description is dense but front-loaded with purpose, then proceeds through code format, operation routing, inference rules, defaults, and the upstream title limitation. Every sentence carries operational information, and there is no filler.

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?

With an output schema present, the description need not explain return shapes, yet it still discloses the bills-row limitation and chaining remedy. It covers all operations, required parameters, defaults, and key behavioral caveats, so an agent has enough to call the tool correctly.

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, but the description adds useful semantics beyond the schema: the committee-code pattern with chamber prefix, name-to-code resolution via 'filter', chamber override behavior, and the bills-specific 'order' default. This meaningfully improves parameter understanding.

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 clearly states the tool browses congressional committees and their legislation, reports, and nominations, with a specific verb and resource. It distinguishes its internal operations well, but does not explicitly differentiate itself from overlapping sibling tools such as congressgov_committee_reports or congressgov_senate_nominations.

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?

It gives explicit operational guidance: use 'list' with optional 'filter' to discover codes, then 'get' or drill into 'bills', 'reports', or 'nominations'; notes that 'nominations' is Senate-only; explains chamber inference and override; and specifies when to chain to congressgov_bill_lookup for titles.

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.