Skip to main content
Glama

capitolguide

by guide.capitol

find_room

Read-only

Find a Capitol office by ROOM CODE (e.g. 'SH-217', '2310 Rayburn', '167 Russell', 'H-232'), by MEMBER NAME (e.g. 'Cornyn', 'Ted Cruz', 'Womack'), or by COMMITTEE ('Senate Judiciary', 'Ways and Means', 'House Armed Services'). A room code returns the decoded location plus who currently holds it; a name returns that member's current office; a committee returns its office / principal hearing room. Member & committee assignments are the 119th Congress (volatile, live-source-stamped).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA room code/address, or a member's name

TDQS

A4.5/5.0
Behavior4/5

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

Annotations (readOnlyHint, openWorldHint) are present; description adds that assignments are 119th Congress, volatile, and live-source-stamped, plus details on what each query returns.

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?

Two concise sentences with no filler, front-loaded with examples and output details; every sentence adds value.

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?

Despite no output schema, description fully explains what each query returns and notes volatility, making it complete for a single-parameter tool with three modes.

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% (one parameter with description), but the tool description adds significant context by explaining the three query types and their results, beyond the schema's generic 'room code or name'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description specifies three distinct query modes (room code, member name, committee) and the output each produces, clearly distinguishing from sibling tools like accessible_route and nearby.

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

Usage Guidelines4/5

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

Describes when to use each query type (room code, name, committee) and implies context (e.g., not for routes/accessibility), but does not explicitly exclude alternatives or mention when not to use.

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

All capitolguide toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: accessibility routes, general routes, access checks, room finding, nearby amenities, operational overview, day planning, prohibited items, and readiness check. No overlap or ambiguity.

Naming Consistency4/5

All tool names use lowercase snake_case and are descriptive. While most follow a verb_noun pattern (e.g., check_access, find_room), a few are noun-only (nearby, overview), but the overall pattern is consistent and predictable.

Tool Count5/5

9 tools is well within the ideal range for a domain-specific server. Each tool serves a necessary function without redundancy, and the count feels appropriate for the Capitol complex navigation and visitor support domain.

Completeness4/5

The tool set covers core domains: navigation, accessibility, room lookup, amenities, security restrictions, and day planning. Minor gaps like event scheduling or tour information exist, but the essential use cases are well-covered.

Resources