Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

Directions routes

routes_directions

The turn-by-turn route between two places, with the distance for each instruction. Use ETA instead when only the travel time is wanted — this asks the provider for more and costs more

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

Input Schema

NameRequiredDescriptionDefault
toNoWhere the journey ends, e.g. 'Heathrow Airport'
fromNoWhere the journey starts, e.g. 'King's Cross, London' (or give from_lat/from_lon)
modeNoHow to travel: drive (default), walk, cycle or transit
to_latNoOptional end latitude, if already known
to_lonNoOptional end longitude, if already known
from_latNoOptional start latitude, if already known
from_lonNoOptional start longitude, if already known
arrive_byNoBe there by this time, as RFC3339. Cannot be combined with depart_at
depart_atNoWhen the journey starts, as RFC3339. Defaults to now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations beyond title are provided, so the description carries the burden. It discloses that the tool is more resource-intensive and returns per-instruction distances. While it doesn't detail response structure, it adds meaningful behavioral context about cost and content beyond what annotations offer.

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, front-loaded with the primary purpose and immediately followed by usage guidance. No wasted 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?

For a tool with 9 parameters and no output schema, the description covers the core behavior and cost trade-off. It mentions the return includes directions with distances, which is essential, though the exact response structure is not fully specified. Schema handles parameter details adequately.

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

Parameters3/5

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

Schema description coverage is 100%, with every parameter having a descriptive comment. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the tool provides a turn-by-turn route between two places with distance for each instruction. This specific verb+resource description distinguishes it from the sibling tool routes_eta, which is explicitly mentioned.

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?

The description gives explicit guidance: 'Use ETA instead when only the travel time is wanted' and explains the trade-off ('this asks the provider for more and costs more'). This clearly directs when to use this tool versus an alternative.

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

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