Skip to main content
Glama

Intercity lanes

list_intercity_lanes
Read-onlyIdempotent

Same-day city-to-city routes: for every launch city, the neighbouring launch cities within 160 km by road (e.g. London → Reading, Leeds → Sheffield, San Francisco → San Jose) with road distance, drive time and a same-day sample price. Longer trips are not offered. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: the 160 km road-distance cutoff, the fact that only launch cities are covered, that longer trips are unavailable, that the call is free, and what fields come back.

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?

The purpose is front-loaded in the first clause, examples are parenthetical and skimmable, and the two trailing fragments ('Longer trips are not offered. Free.') each carry distinct constraint information. The opening sentence is long but every clause earns its place.

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?

With no input parameters and no output schema, the description carries the burden of describing returns, and it does so (road distance, drive time, same-day sample price) while also bounding the dataset. Only volume or enumeration behaviour for a no-argument listing call is left unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The definition correctly uses its space to describe scope and output rather than parameter syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb-and-resource framing ('Same-day city-to-city routes') plus the exact rule for inclusion (neighbouring launch cities within 160 km by road) and concrete examples. An agent can tell this is the lane catalog rather than a quoting tool, though it never names the sibling get_intercity_quote explicitly.

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

Usage Guidelines3/5

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

It states a clear boundary ('Longer trips are not offered') and a cost fact ('Free'), which implicitly tells the agent when this tool applies and when it does not. However, there is no explicit routing to the alternative for priced or long-distance queries, so the agent must infer that get_intercity_quote handles those.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.