Skip to main content
Glama
Sign In

atlas

by com.trainrouter
OverviewDiscussionsAdmin

Get one route in full

get_route
Read-onlyIdempotent

Full record for one atlas route by exact id: distance, fastest time, top speed, operator, rolling stock, opening year, ridership, story, on-route sights, photo and page URL, plus country-hub links. An unknown id returns up to 5 close-match suggestions instead of failing. Use search_routes first when you only have a name or city.

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": {
      "id": "<id>"
    },
    "name": "get_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact route id in kebab-case, e.g. "glacier-express" — take it from search_routes, famous_routes or routes_in_country results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Route id, e.g. \"glacier-express\""New value: +"Exact route id in kebab-case, e.g. \"glacier-express\" — take it from search_routes, famous_routes or routes_in_country results."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds genuinely non-obvious behavior: an unknown id returns up to 5 close-match suggestions rather than failing, which changes how an agent should handle a miss. It stops short of noting result limits or ordering details for those suggestions.

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?

Front-loaded with the core verb and resource, then the fallback behavior, then the disambiguation rule. The long field list earns its place because there is no output schema and it substitutes for one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one well-documented parameter, safe annotations, and no output schema, the description covers everything an agent needs: what comes back, what happens on a bad id, and when to prefer a sibling tool.

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 coverage is 100% and the single id parameter already documents kebab-case format plus the source tools (search_routes, famous_routes, routes_in_country). The description restates "exact id" but adds no format or normalization guidance beyond the schema, so baseline 3 applies.

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 ("Full record for one atlas route by exact id") and enumerates the payload (distance, time, top speed, operator, rolling stock, opening year, ridership, story, sights, photo/URL, country-hub links). This is clearly distinguishable from search_routes, famous_routes, and routes_in_country, which are list/filter 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 routes the agent: "Use search_routes first when you only have a name or city." That names the alternative and the condition that selects it, and it defines the required input as an exact id.

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

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