capitolguide

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).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "route_between"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Destination: room code, building name, or Metro station / landmark
`from`	Yes	Origin: room code, building name, or Metro station / landmark (e.g. 'Capitol South Metro')
`accessible`	No	Prefer a step-free / accessible route

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJun 12, 2026

changedInput schema / properties / from / description

Previous value: -"Origin room code or building name"New value: +"Origin: room code, building name, or Metro station / landmark (e.g. 'Capitol South Metro')"

changedInput schema / properties / to / description

Previous value: -"Destination room code or building name"New value: +"Destination: room code, building name, or Metro station / landmark"

First observedJun 11, 2026

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?