Skip to main content
Glama
Sign In

capitolguide

by guide.capitol
OverviewDiscussionsAdmin

accessible_route

Read-only

Step-free / accessible directions between two points in the Capitol complex by mobility profile (wheelchair, limited_mobility, stroller, low_vision). Routes over elevators/ramps only, avoids stairs, and surfaces OCAS accommodation contacts. Use this instead of route_between when step-free matters.

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": "accessible_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination: room code, building name, or Metro station / landmark
fromYesOrigin: room code, building name, or Metro station / landmark (e.g. 'Union Station')
mobility_profileNoMobility profile (default: any step-free)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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. 'Union Station')"
    • changedInput schema / properties / to / description
      Previous value: -"Destination room code or building name"New value: +"Destination: room code, building name, or Metro station / landmark"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: it avoids stairs, uses elevators/ramps, and surfaces OCAS accommodation contacts. No contradiction with readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence contains all key information efficiently, but could be broken into multiple sentences for slightly better readability.

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 purpose, when to use, and parameters well. However, lacks description of output format (e.g., steps, map, contacts), which would be helpful given no output schema.

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%, and the description adds meaning by noting default mobility profile and examples for from/to (e.g., 'Union Station'). It also lists the enum values explicitly.

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?

The description states it provides step-free accessible directions between two points in the Capitol complex, using specific mobility profiles. It also distinguishes itself from the sibling tool 'route_between' by emphasizing step-free routing.

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

Usage Guidelines5/5

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

Explicitly says 'Use this instead of route_between when step-free matters', providing clear guidance on when to use and the alternative.

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