Skip to main content
Glama

Piratefly Flight Price Judge

Which months are cheapest for this route

cheapest_months
Read-onlyIdempotent

The departure months ranked by observed median price for a route, with the median of each. Answers "when is it cheapest to go" with measured data instead of seasonal folklore.

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

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.5/5.0
Behavior3/5

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

Annotations already carry the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful data-provenance context by saying ranks come from observed medians rather than seasonality assumptions, but it says nothing about data coverage windows, empty/no-data routes, or result length.

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?

One sentence that front-loads the return shape (ranked months with medians) followed by the question it answers. The 'seasonal folklore' clause is mildly rhetorical but does convey that the data is measured; little genuine waste.

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 output schema, the description does its job by describing the return: months ordered by median price, each with its median. Gaps remain around data coverage/recency and behavior on routes with sparse data, but nothing essential for calling it is missing.

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 already document the city-name-only constraint with examples. The description adds only the framing that inputs define a 'route'; no syntax or format detail beyond the schema, so 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?

States a specific output: departure months ranked by observed median price for a route, with each month's median. The resource (months for a route) is clear and distinguishable from flight_price_verdict and when_to_book. It never names a sibling explicitly, so it isn't fully differentiated.

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 "when is it cheapest to go"' implies the use case, but there is no explicit when-to-use vs. when-to-use-something-else guidance. The closest sibling, when_to_book, is about advance-purchase timing and is never mentioned or excluded, leaving the agent to infer the boundary.

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