Skip to main content
Glama

get_congress_committees

Retrieve a list of U.S. Congressional committees, optionally filtered by chamber (House or Senate) and Congress number (100–120).

Instructions

Get list of Congressional committees

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_congress_committees"
  }
}

Input Schema

NameRequiredDescriptionDefault
chamberNoChamber filter (House or Senate)
congressNoCongress number (e.g., 118 for current Congress)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden, yet it only implies a read operation via "Get list." It does not state whether subcommittees are included, whether results are paginated or bounded, or what the list entries contain, all of which matter for a reference-data lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and wastes no words, but its brevity stems from under-specification rather than disciplined editing. It is concise without being informative.

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

Completeness2/5

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

For a simple two-optional-parameter read tool with a fully documented schema and no output schema, the description could reasonably say what the returned list contains and whether both filters are independently applicable. As written it leaves the agent to discover the semantics of an unfiltered call on its own.

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%, with the chamber enum and congress range (100-120) both documented inline. The description adds no meaning beyond those fields, so the baseline of 3 applies since the schema does the work.

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 names a specific verb and resource ("Get list of Congressional committees"), which is unambiguous about what the tool returns. It offers no explicit contrast with siblings such as search_congress_bills, though the resource itself is distinct enough that an agent would not confuse them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no named alternative. The agent is left to infer that this is the tool for committee lookup whenever committee data is needed, and must guess how it relates to the bill-oriented siblings.

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