Skip to main content
Glama

cheapest_days

Find daily low-cost Ouigo fares between two stations across a date range and get booking links for Ouigo and Iryo pages.

Instructions

Cheapest Ouigo price per day between start and end (YYYY-MM-DD). The result has shop (Ouigo booking page) and iryo (Iryo page, no prices) for the cheapest 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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "cheapest_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
originYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral load, and it does disclose something useful: the result is keyed to the single cheapest day and carries separate `shop` (Ouigo) and `iryo` (Iryo, no prices) entries. It says nothing about whether results are live-queried, how far ahead data is valid, rate limits, or how many days are returned.

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?

Two short sentences, front-loaded with the core purpose and followed by the result structure. The trailing 'give both' is terse to the point of being cryptic, but nothing is padded or redundant.

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?

A four-required-parameter search tool with no annotations and no output schema needs the description to cover input formats and return shape; it covers the return shape at a high level and the date formats, but leaves origin/destination semantics undefined. Adequate to attempt a call, not adequate to call correctly with confidence.

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?

Schema description coverage is 0%, so the description must define all four parameters and only partially does: start and end are given the YYYY-MM-DD format. Origin and destination are entirely unqualified — no indication whether they take station names, IDs, or city codes, which is the main ambiguity for a rail-search call.

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?

Names a specific resource and metric: the cheapest Ouigo price per day across a start/end date range. The verb is implied ('find cheapest') rather than stated, and no sibling is referenced, so an agent can infer the purpose but gets no explicit differentiation from search_trains or shop_link.

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?

Usage is implied by the date-range framing: call it when you want a per-day price comparison over a window rather than a single itinerary. There are no stated exclusions or prerequisites and no named alternative, and the only procedural instruction ('give both') concerns how to present results rather than when to call.

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