Skip to main content
Glama

get_committee

Read-only

Fetch a committee’s members with positions and scheduled meetings by committee ID or partial name for quick legislative review.

Instructions

Get a committee's members (with positions) and scheduled meetings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "committee": "<committee>"
    },
    "name": "get_committee"
  }
}

Input Schema

NameRequiredDescriptionDefault
committeeYesCommittee id (e.g. 'INTBUS') or part of its name.
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

A3.6/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 the safety profile is covered. The description adds useful scope by saying the response bundles both members and meetings, but it never mentions truncation behavior or the server default behind the character budget, which matters for a read that can return a large roster.

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?

A single short sentence with the resource and the returned content front-loaded; no filler or redundant restatement of the name.

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

Completeness4/5

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

For a two-parameter read-only tool with full schema coverage, no output schema and safe annotations, the description covers the essentials and helpfully names what comes back (members with positions, meetings). Only match-failure and truncation behavior are unaddressed.

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 coverage is 100%, so both parameters are already documented, including the id-or-partial-name matching and the 500-20000 character range. The description adds nothing about the resolution rules for partial names or how truncation is signalled, so it sits at the baseline.

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?

States a specific verb ('Get') and resource ('a committee's members... and scheduled meetings'), and the parenthetical '(with positions)' tells the agent what the payload includes. It is clear enough to distinguish from list_committees, though it never names that or any other sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: pass a committee id or partial name to retrieve that committee's detail. There is no statement of when to prefer this over list_committees or get_meeting_calendar, and no note on what happens when no match is found.

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