Skip to main content
Glama
Sign In

atlas

by com.trainrouter
OverviewDiscussionsAdmin

Night trains / sleepers

night_trains
Read-onlyIdempotent

Sleeper routes from the atlas, sorted by renown — all of them by default, or only those starting or ending in a given city — with the per-city night-train guide URL when one exists. Use for overnight and sleeper questions; city_pair for concrete A-to-B times; search_routes for other route categories.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city filter matched against route endpoints (accent-insensitive), e.g. "Vienna".

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 / city / description
      Previous value: -"Optional city, e.g. \"Vienna\""New value: +"Optional city filter matched against route endpoints (accent-insensitive), e.g. \"Vienna\"."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-open-world lookup. The description adds useful behavior: results are sorted by renown, all routes are returned by default, city matching applies to route endpoints, and guide URLs are included only when present.

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?

The description is compact and front-loaded: it states the core behavior first, then the filtering option, then the sibling routing guidance. Every clause adds useful information without repetition.

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?

For a single-parameter read-only lookup with no output schema, it covers the essential context: default scope, sorting, filtering behavior, return enrichment via guide URLs, and when to use sibling tools. Nothing needed to invoke it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents the city parameter and its accent-insensitive matching. The description adds interpretation by clarifying that city filtering means routes starting or ending in that city, which is meaningfully more specific than the schema alone.

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 names a specific resource — sleeper routes from the atlas — and states its scope, sorting, optional city filter, and inclusion of guide URLs. It also distinguishes itself from city_pair and search_routes by naming them directly.

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?

It explicitly says to use this for overnight and sleeper questions, then routes concrete A-to-B time queries to city_pair and other route categories to search_routes. The when-to-use and alternatives are both clear.

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