Ready APIs

Flight Cancellation Risk

flight_cancellation_risk

Read-onlyIdempotent

Return historical cancellation-risk signals for a route. This is not live tracking.

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

Input Schema

Name	Required	Description
`dest`	Yes	Destination airport code, for example LGA.
`month`	No	Optional numeric month.
`origin`	Yes	Origin airport code, for example ATL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful temporal context with 'historical' and 'not live tracking,' but it does not disclose the signal format, lookback period, or granularity, so some behavioral detail remains implicit.

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 with no filler. The first sentence states the core capability, and the second sentence prevents misuse by clarifying this is not live tracking. Every word earns its place.

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?

The tool is simple with only two required parameters, and annotations cover safety semantics. However, because there is no output schema, the description should clarify what 'signals' actually look like, such as fields, units, or possible values, which is currently left to inference.

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 100%, so the parameters are already documented fully in the schema. The description adds no parameter-specific meaning beyond routing, which is acceptable under the baseline for fully covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Return'), resource ('historical cancellation-risk signals'), and scope ('for a route'). The phrase 'not live tracking' distinguishes it from live flight-status tools and implies it is not a real-time tracker, separating it clearly from sibling flight tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear use case: obtaining historical route cancellation-risk signals. It also gives an explicit when-not boundary with 'This is not live tracking.' It does not name alternatives like flight_reliability or flight_route_summary, so it stops short of full routing guidance.

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

All Ready APIs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?