Skip to main content
Glama

capitolguide

by guide.capitol

route_between

Read-only

Turn-by-turn directions between two points in the Capitol complex. Each point can be a room code, a building name, OR a Metro station / landmark (e.g. 'Capitol South Metro' → '2412 Rayburn', 'Union Station' → '517 Hart', or to the 'Supreme Court' / 'Library of Congress'). Returns an ordered step list with mode (walk/tunnel/subway), minutes, and a flag wherever you re-clear security. Set accessible=true for a step-free route (or use accessible_route).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesDestination: room code, building name, or Metro station / landmark
fromYesOrigin: room code, building name, or Metro station / landmark (e.g. 'Capitol South Metro')
accessibleNoPrefer a step-free / accessible route

TDQS

A4.7/5.0
Behavior5/5

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

Description discloses return format ('ordered step list with mode, minutes, and a flag wherever you re-clear security'). Annotations already declare readOnlyHint=true and openWorldHint=true, but description adds behavioral details about security checks.

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?

Single paragraph of 4 sentences, front-loads the core purpose, then gives parameter details, return format, and a tip. No redundant words.

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?

Covers input examples, parameter effects, return structure, and alternative tool. Without output schema, it provides enough for an agent to understand the tool's output. Minor missing detail: whether route is optimal or time-based, but sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning: explains what 'from' and 'to' can be (room code, building, Metro, landmark) with concrete examples, and clarifies 'accessible' parameter results in step-free route.

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 clearly states it provides 'turn-by-turn directions between two points in the Capitol complex' and specifies the types of points (room code, building, Metro station/landmark). Examples distinguish it from sibling tool 'accessible_route'.

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?

Description explains when to use: for directions in the Capitol complex, and mentions setting 'accessible=true' or using 'accessible_route' for step-free routes. It does not explicitly state when not to use, but provides enough context.

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