Skip to main content
Glama

Piratefly Flight Price Judge

How far ahead to book this route

when_to_book
Read-onlyIdempotent

How many days before departure this route has historically been cheapest, from our own observations. Answers "am I booking too early or too late?".

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>"
    },
    "name": "when_to_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesOrigin CITY NAME, e.g. "Milan". Airport codes are not accepted.
destinationYesDestination CITY NAME, e.g. "Tokyo". Airport codes are not accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real value on top: "from our own observations" discloses that the answer is a historical, first-party estimate rather than authoritative carrier data — a caveat an agent needs before relaying it to a user. It does not say what happens when a route has no observation history, which keeps it below 5.

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 tight sentences: the metric first, the user question it answers second. No filler, no restating of the title, and the core output is front-loaded.

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?

With no output schema, the description carries the burden of describing the return, and "how many days before departure" only implies a single number — it does not say whether it comes back as an integer, a range, or with confidence/data-coverage info, nor how a route with no history is reported. Adequate for a simple two-param lookup, but these gaps matter for an estimate-style 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 both parameters carry explicit city-name-with-no-airport-codes guidance, so the schema does the heavy lifting. The description adds nothing about the parameters themselves; baseline 3 applies.

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?

The description states a specific metric — the historical cheapest-days-before-departure window for a given route — which an agent can distinguish from cheapest_months (monthly seasonality) and flight_price_verdict (current price judgment). It is clear but never names those siblings, so differentiation is left partly to inference.

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?

"Answers 'am I booking too early or too late?'" gives a situational framing for when this tool is relevant, which is better than nothing. But there is no explicit 'when not to use' and no routing to cheapest_months or flight_price_verdict, so the agent must work out the boundaries itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources