Skip to main content
Glama
Sign In

divux

by si.divux
OverviewDiscussionsAdmin

Trip check: destination advice, fares and airport delays

check_trip
Read-only

Returns, for the inputs that are present: destination advice for a country (US State Department, UK FCDO and Canada, side by side), active disaster alerts, weather for the city being visited (pass city; defaults to the capital), CDC travel health notices, public holidays between two dates, and an exchange rate; the cheapest round-trip or one-way fares recently found for a route (dates, airline, stops, booking links), which are cached finds and not live quotes; a per-leg total for up to four planned legs, in USD and a local currency; and FAA delay reports for US airport codes (ground stops, delay programs, arrival and departure delays, closures). Booking links may be paid links. Divux does not book flights. Applies to questions about travel to a country, flight prices on a route, or current delays at US airports. Results report what the official sources say and are not a safety assessment of a destination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoFor fares: destination city, airport code, or metro, e.g. 'Lisbon' or 'Tokyo'; defaults to city, then the country's capital
cityNoCity being visited, for weather, e.g. 'Kyoto' or 'Lisbon'.
fromNoFor fares: departure city, airport code, or metro, e.g. 'New York', 'JFK', or 'Bay Area'
legsNoUp to four flight legs. The result is cached cheapest fares per leg, by day, and a trip total.
departNoFor fares: departure month YYYY-MM or date YYYY-MM-DD; defaults to start_date
returnNoFor fares: return month or date; defaults to end_date; leave both out for one-way
countryNoDestination country in English or two-letter code, e.g. 'Japan' or 'JP'
one_wayNoFor fares: true for one-way; defaults to one-way when there's no return
airportsNoUS airport codes for the FAA's delays right now, e.g. ['SFO', 'JFK']; an empty list for every US airport with a delay
end_dateNoTrip end, YYYY-MM-DD
start_dateNoTrip start, YYYY-MM-DD
direct_onlyNoFor fares: true for nonstop flights only
home_currencyNoTraveler's currency, e.g. 'USD'
local_currencyNoDestination currency, e.g. 'JPY'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / to / description
      Previous value: -"For fares: destination city, airport code, or metro, e.g. 'Lisbon' or 'Tokyo'; defaults to the country's capital"New value: +"For fares: destination city, airport code, or metro, e.g. 'Lisbon' or 'Tokyo'; defaults to city, then the country's capital"
  2. Changed3 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City being visited, for weather, e.g. 'Kyoto' or 'Lisbon'.",
+  "maxLength": 80,
+  "type": "string"
+}
    • removedInput schema / properties / lat
      Removed value: -{
-  "description": "Latitude of the place being visited, for weather",
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}
    • removedInput schema / properties / lon
      Removed value: -{
-  "description": "Longitude of the place being visited, for weather",
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}
  3. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"For fares: departure city or airport code, e.g. 'New York' or 'JFK'"New value: +"For fares: departure city, airport code, or metro, e.g. 'New York', 'JFK', or 'Bay Area'"
    • changedInput schema / properties / to / description
      Previous value: -"For fares: destination city or airport code, e.g. 'Lisbon'; defaults to the country's capital"New value: +"For fares: destination city, airport code, or metro, e.g. 'Lisbon' or 'Tokyo'; defaults to the country's capital"
  4. Changed1 schema field changed
    • changedInput schema / properties / legs / description
      Previous value: -"To price a trip you planned: each flight leg (max 4). Returns cached cheapest fares per leg, by day, and a trip total"New value: +"Up to four flight legs. The result is cached cheapest fares per leg, by day, and a trip total."
  5. Changed1 schema field changed
    • addedInput schema / properties / legs
      Added value: +{
+  "description": "To price a trip you planned: each flight leg (max 4). Returns cached cheapest fares per leg, by day, and a trip total",
+  "items": {
+    "properties": {
+      "depart": {
+        "description": "YYYY-MM or YYYY-MM-DD",
+        "maxLength": 10,
+        "type": "string"
+      },
+      "direct_only": {
+        "type": "boolean"
+      },
+      "from": {
+        "maxLength": 60,
+        "minLength": 2,
+        "type": "string"
+      },
+      "nights": {
+        "maximum": 60,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "return": {
+        "description": "Omit for one-way",
+        "maxLength": 10,
+        "type": "string"
+      },
+      "to": {
+        "maxLength": 60,
+        "minLength": 2,
+        "type": "string"
+      },
+      "travellers": {
+        "description": "Default 1",
+        "maximum": 9,
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "from",
+      "to",
+      "depart"
+    ],
+    "type": "object"
+  },
+  "maxItems": 4,
+  "type": "array"
+}
  6. Changed9 schema fields changed
    • addedInput schema / properties / airports
      Added value: +{
+  "description": "US airport codes for the FAA's delays right now, e.g. ['SFO', 'JFK']; an empty list for every US airport with a delay",
+  "items": {
+    "maxLength": 4,
+    "minLength": 3,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • changedInput schema / properties / country / description
      Previous value: -"Country name in English or two-letter code, e.g. 'Japan' or 'JP'"New value: +"Destination country in English or two-letter code, e.g. 'Japan' or 'JP'"
    • addedInput schema / properties / depart
      Added value: +{
+  "description": "For fares: departure month YYYY-MM or date YYYY-MM-DD; defaults to start_date",
+  "maxLength": 10,
+  "type": "string"
+}
    • addedInput schema / properties / direct_only
      Added value: +{
+  "description": "For fares: true for nonstop flights only",
+  "type": "boolean"
+}
    • addedInput schema / properties / from
      Added value: +{
+  "description": "For fares: departure city or airport code, e.g. 'New York' or 'JFK'",
+  "maxLength": 60,
+  "type": "string"
+}
    • addedInput schema / properties / one_way
      Added value: +{
+  "description": "For fares: true for one-way; defaults to one-way when there's no return",
+  "type": "boolean"
+}
    • addedInput schema / properties / return
      Added value: +{
+  "description": "For fares: return month or date; defaults to end_date; leave both out for one-way",
+  "maxLength": 10,
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "For fares: destination city or airport code, e.g. 'Lisbon'; defaults to the country's capital",
+  "maxLength": 60,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "country"
-]
  7. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover read-only and open-world, but the description adds materially: fares are 'cached finds and not live quotes', booking links 'may be paid links', the service does not book flights, and results are not a safety assessment. It also discloses input-conditional behavior ('for the inputs that are present') and the capital-city fallback for weather, which the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead clause 'Returns, for the inputs that are present' is a good front-load, and the closing applicability sentence is well placed. However, the middle is a single sprawling sentence chaining eight unrelated capabilities, which is hard to scan for a 14-parameter multi-purpose tool; bullets or semicolon-grouped capability blocks would carry the same content with less cognitive cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 optional parameters, no output schema, and five distinct capability clusters, the description is complete enough to call correctly: it says what each cluster returns (fares with dates, airline, stops, booking links; delays with ground stops, delay programs, closures), which inputs activate which cluster, and what the results are not. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description goes beyond it by tying parameters to specific outputs (pass `city` for weather, which defaults to the capital; `airports` gives FAA delays; dates drive holiday lookup; legs produce a total in USD plus a local currency). The pairing of home_currency/local_currency and the defaulting of `depart`/`return` to the trip dates are explained in prose elsewhere in the schema, so gains are incremental rather than decisive.

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 enumerates concrete resources and verbs: destination advice, disaster alerts, weather, CDC notices, public holidays, exchange rate, cached fares, per-leg totals, and FAA delay reports. It also states the application domains (travel to a country, flight prices on a route, current US airport delays), which separates it from generic 'check_place' style siblings. It stops short of naming or contrasting any sibling tool explicitly, which keeps it out of the 5 band.

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?

'Applies to questions about travel to a country, flight prices on a route, or current delays at US airports' gives clear trigger conditions, and 'Divux does not book flights' plus 'not a safety assessment' mark boundaries. There is no explicit when-not or named alternative for overlapping needs (e.g., destination background vs. general place lookup), so it is strong context without 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 divux toolsInspect
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