Skip to main content
Glama

search_trains

Find Ouigo train fares for a specific route and date, sorted cheapest first, plus booking links and Iryo schedules for that day. Use it to compare prices before booking.

Instructions

Ouigo trains and prices for one day (YYYY-MM-DD), cheapest first. Slow (~5-10 s). The result has shop (Ouigo booking page) and iryo (Iryo page, no prices) for this day: give both.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "date": "<date>"
    },
    "name": "search_trains"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
originYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose unusual behavior: the ~5-10 s latency and the fact that the result contains two source blocks, one of which ('iryo') carries no prices. It says nothing about authentication, empty results, or error behavior for a network call.

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 short sentences, front-loaded with the resource and sort order, then the latency warning and output shape. No filler.

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

Completeness3/5

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

It partially covers the return shape (shop/iryo keys) despite there being no output schema, and flags cost via latency, but omits the origin/destination input format and any failure behavior for what is an unannotated network tool.

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

Parameters2/5

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

All three parameters are required with 0% schema description coverage, so the description must compensate. It only documents the date format (YYYY-MM-DD); it says nothing about whether origin/destination are station codes, station names, or city names, which matters given a sibling exists for station lookup.

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?

States a specific verb and resource: trains and prices for a single day, with an explicit ordering rule ('cheapest first'), which implicitly distinguishes it from the day-finding sibling. It stops short of naming the sibling it replaces for multi-day or cheapest-day searches.

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?

The 'give both' instruction plus the latency note ('Slow (~5-10 s)') imply the usage context and warn the agent that this is an expensive call, but there is no explicit when-to-use versus cheapest_days, find_station, or shop_link.

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