get_congress_member
Get a single Congress member by bioguide ID.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Bioguide ID |
simplefunctions
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry full behavioral disclosure. It only states the action ('Get') and the input, without mentioning return format, potential errors, or any special behavior. For a simple read tool this is minimal but still lacks context that could help an agent anticipate outcomes.
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 a single sentence containing only the essential information: action, resource, and identifier. It is concise, front-loaded, and free of unnecessary detail.
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 tool is simple with one parameter and no output schema, but the description does not explain what is returned or any prerequisites. Given the minimal complexity, the description is adequate but lacks completeness that could help an agent know what to expect after invocation.
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?
The schema fully covers the single parameter 'id' with description 'Bioguide ID', and the description confirms this by saying 'by bioguide ID'. Since schema coverage is 100%, the description adds no new semantic information but reinforces the key concept, matching the baseline of 3.
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 gets a single Congress member by bioguide ID, using a specific verb and resource. It distinguishes from sibling tools like list_congress_members through the word 'single', though it does not explicitly name alternatives.
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 implied: use this tool when you need a specific Congress member by bioguide ID. However, there is no explicit guidance on when to use this versus list_congress_members or other retrieval tools, and no exclusions are provided.
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.
TDQS
C2.8/5.0
Disambiguation2/5
Many tools have overlapping purposes, such as multiple market query tools (scan_markets, screen_markets, get_market_detail, get_market_diff, get_market_history, inspect_ticker) and legislative tools (legislation, get_legislation, list_legislation, query_gov). Aliases like get_heartbeat_config/get_heartbeat_status and explore_public/explore_theses add further confusion. An agent would struggle to select the correct tool without deeply reading each description.
Naming Consistency3/5
Most tools follow a verb_noun pattern (get_, list_, create_, update_), but there are notable deviations: 'legislation' lacks the 'get_' prefix, 'stt' and 'tts' are acronyms, 'monitor_the_situation' is a full phrase, and 'x_account/x_news/x_volume' use a non-standard prefix. The overall style is readable, but the mixed conventions reduce predictability.
Tool Count1/5
108 tools is extreme for any server, even one covering prediction markets, trading, portfolio management, forum, skills, and speech. The massive surface area overwhelms agents and makes the server feel more like a platform than a coherent toolkit. This many tools inevitably leads to redundancy and maintenance burden.
Completeness4/5
The server covers an impressively broad domain: market data, thesis management, intents, strategies, positions, portfolio, forum, skills, legislative and economic queries, and audio/visual processing. Minor gaps exist (e.g., no delete for skills/theses, no update for some portfolio items) but core workflows are well-supported. Overall lifecycle coverage for most entities is strong.