Skip to main content
Glama

rank_routes

Read-only

Ranks 17 California corridors by live activity or measured congestion to show which routes are busiest now, with counts and a one-line reason explaining each ranking.

Instructions

CALIFORNIA ONLY: which of 17 curated California corridors have the most going on right now.

Answers "what are the busiest routes in California", "which California highways should I avoid today". Not for other states: for a place elsewhere use get_nearby_events or get_traffic.

by="activity" ranks on live events (full closures weigh most, then incidents, lane closures, chain controls); by="congestion" ranks on measured speed vs free-flow at each corridor's midpoint and needs the traffic feed to be configured - if it is not, the ranking silently falls back to activity.

Each entry carries the counts and a one-line reason, so the answer can say WHY a corridor ranks where it does, not just list names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rank_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoactivity
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.82.1

TDQS

A4.5/5.0
Behavior4/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the ranking weights per mode, that congestion mode depends on a configured traffic feed, and that a missing feed causes a silent fallback to activity. That silent-fallback warning is exactly the kind of surprise an agent needs. It stops short of covering error behavior or latency, so not a 5.

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?

Front-loaded with the scope constraint, then the use/avoid guidance, then the mode semantics and return shape. Every block is useful, though the quoted example questions are slightly redundant given the explicit statement that precedes them.

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?

There is no output schema, so the description correctly compensates by saying each entry carries counts and a one-line reason, which tells the agent what it can report. Only the 'limit' parameter and any empty-result behavior remain unexplained.

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?

With 0% schema coverage the description carries the full burden, and it does explain the important 'by' parameter in depth, including the factors each mode weighs and the congestion fallback. The 'limit' parameter is never mentioned, leaving its meaning and default (5) to the bare schema title.

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?

States a specific verb and resource with hard scope: 'which of 17 curated California corridors have the most going on right now'. The 'CALIFORNIA ONLY' framing makes it immediately distinguishable from the broader get_traffic / get_nearby_events siblings.

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 names both when to use it ('what are the busiest routes in California') and when not to ('Not for other states'), and routes the agent to two concrete alternatives, get_nearby_events and get_traffic. It also distinguishes the two modes of the tool itself, activity vs congestion.

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