Skip to main content
Glama

iryo_link

Generates an Iryo booking page link for a given origin, destination and travel date so users can open it, choose options and pay on Iryo's site. No fares are returned.

Instructions

Iryo's own booking page for this trip (YYYY-MM-DD), as a link. Iryo gives no fares through this tool: hand the link to the user, who opens it and picks and pays there. Does not open a browser. "Madrid" means all Madrid stations; a warning field flags pairs Iryo is known not to run.

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

Input Schema

NameRequiredDescriptionDefault
dateYes
originYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it says no fares are returned, that the link is handed to the user rather than opened, and that a `warning` field flags routes Iryo is known not to run. Remaining gaps are error/failure behavior and what happens when no link exists.

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?

Three short sentences, front-loaded with what the tool returns and why, then the operational constraint, then the edge-case semantics. Minimal waste; only the trailing warning/Madrid sentence feels slightly tacked on.

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 annotations and no output schema, the description still covers the return shape (link plus a `warning` field), the payment handoff model, and key parameter conventions. What is missing — behavior on unavailable routes or invalid station pairs — is modest for a link-generating 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 description coverage is 0% across three required parameters, so the description has to compensate and partially does: it pins the date format (YYYY-MM-DD) and defines that 'Madrid' means all Madrid stations. Origin/destination matching rules beyond that example, and normalization expectations, remain unstated.

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: returns Iryo's own booking page link for a given trip, with the date format shown inline. It differentiates itself from fare-search siblings by declaring 'Iryo gives no fares through this tool', though it does not name the sibling an agent should use instead.

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?

Gives clear downstream usage — hand the link to the user, who picks and pays there — and implies that fare lookups belong elsewhere. It stops short of an explicit when-to-use/when-not-to-use rule or naming an alternative for pricing workflows.

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