Skip to main content
Glama

list_committees

Read-only

Retrieve legislative committees with chair, member count, and next meeting time in UTC, with search, paging, and response-size controls for focused results.

Instructions

List legislative committees with chair, member count and next meeting (UTC).

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": "list_committees"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-50).
queryNoOnly committees whose name or id contains this.
offsetNoStart position for paging; use next_offset from a prior call.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful detail that meeting times are in UTC and what each item contains, but says nothing about paging behavior, result ordering, or empty-result behavior despite a paging-oriented schema.

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?

A single dense sentence with the core action front-loaded and no filler. It could have gone one clause further to cover paging or alternatives at no real cost.

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

Completeness3/5

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

The absent output schema makes the returned-field summary genuinely valuable, and the UTC note is a good touch. But for a paginated list tool with a char-budget parameter, the description omits pagination flow and how to escalate to get_committee for details.

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 limit, query, offset and max_chars all documented in-schema. The description adds no parameter detail beyond that, so baseline 3 applies.

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 gives a specific verb and resource ('List legislative committees') and names the fields returned (chair, member count, next meeting in UTC). It doesn't explicitly distinguish itself from the sibling get_committee, though the list/get contrast is reasonably self-evident from the names.

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 pointer to get_committee for single-committee detail. The name implies a browsing use case, but the definition itself never says so.

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