Jet Tracker

Trip cost between two airports

jt_trip_cost

Read-onlyIdempotent

Cost of a trip origin to destination (ICAO codes or city names) for a model with a full cost profile, across charter, fractional and owned (variable cost only) models, with distance and block time. Same aliases as jt_compute_tco. Origin equal to destination returns error degenerate_route.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Modelo com calculadora completa (mesmos aliases do compute_tco).
`destIcao`	Yes	Destino: ICAO ou cidade/nome.
`roundTrip`	No	true = ida e volta (default); false = só ida.
`originIcao`	Yes	Origem: ICAO (SBSP) ou cidade/nome (Congonhas, São Paulo).

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Machine-readable error code (INTERNAL, TIMEOUT, INVALID_ARGUMENT, NOT_FOUND, TOOL_FAILED, ACCOUNT_KEY_REQUIRED).
`_meta`	No
`error`	No
`found`	No
`gated`	No
`requestId`	No
`retryable`	No
`quota_exceeded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / properties / _meta / required

Previous value: -[
-  "tool",
-  "tier",
-  "source",
-  "asOf",
-  "gated",
-  "via"
-]New value: +[
+  "tool",
+  "source",
+  "asOf",
+  "gated",
+  "via"
+]

Changed12 schema fields changedSep 16, 2026

changedInput schema / properties / slug / description

Previous value: -"Slug de modelo com calculadora completa: embraer-phenom-100, embraer-phenom-300, beechcraft-hawker-400xp, leonardo-aw109 ou airbus-h125."New value: +"Modelo com calculadora completa (mesmos aliases do compute_tco)."

removedInput schema / properties / slug / enum

Removed value: -[
-  "embraer-phenom-100",
-  "embraer-phenom-300",
-  "beechcraft-hawker-400xp",
-  "leonardo-aw109",
-  "airbus-h125"
-]

addedInput schema / properties / slug / maxLength
```
Added value: +80
```
addedInput schema / properties / slug / minLength
```
Added value: +2
```
addedOutput schema / properties / _meta / properties / asOf / description
```
Added value: +"Alias of sourceUpdatedAt (kept for compatibility)."
```

addedOutput schema / properties / _meta / properties / generatedAt

Added value: +{
+  "description": "When this response was produced (ISO 8601).",
+  "type": "string"
+}

addedOutput schema / properties / _meta / properties / observedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Last event actually observed in the data returned (last flight, last arrival, last listing sighting)."
+}

addedOutput schema / properties / _meta / properties / sourceUpdatedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Last sync of the underlying source (RAB snapshot, registry import, listing scan). Never in the future."
+}

addedOutput schema / properties / _meta / properties / validUntil

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Expiry of the fact returned, when it has one (CVA validity, period end)."
+}

addedOutput schema / properties / code

Added value: +{
+  "description": "Machine-readable error code (INTERNAL, TIMEOUT, INVALID_ARGUMENT, NOT_FOUND, TOOL_FAILED, ACCOUNT_KEY_REQUIRED).",
+  "type": "string"
+}

addedOutput schema / properties / requestId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

First observedSep 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish the safe read/idempotent profile, and the description adds real behavioral detail beyond them: the cost basis distinction (owned models yield variable cost only), the inclusion of distance and block time in the result, and the degenerate_route error when origin equals destination. It does not cover casing/normalization of city names or rate/unit behavior, keeping it from a 5.

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?

Two compact sentences with the core purpose front-loaded and the error condition placed at the end where it belongs. The middle clause listing the three model categories makes it slightly dense but every phrase carries information.

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 an output schema present, the description needn't explain return shape, yet it still names the key outputs; parameters and annotations are covered. For a 4-parameter read tool this is nearly complete, with only the cross-tool selection guidance and parameter-format details 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 description coverage is 100%, so the schema already documents all four parameters, and the description largely restates them (ICAO or city names, full cost profile model). It adds marginal value — the 'variable cost only' caveat for owned models — but does not explain the roundTrip default or naming/alias semantics beyond what the schema shows. Baseline 3.

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 verb and resource — 'cost of a trip origin to destination' — and enumerates the model categories (charter, fractional, owned) plus the returned metrics (distance, block time). It is clearly distinguishable from generic lookup siblings. It stops short of a 5 because the sibling relationship is only implied via the alias reference to jt_compute_tco rather than an explicit contrast of scope.

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?

Usage is implied by the wording (compute a route cost for a model with a full cost profile) and the error precondition 'origin equal to destination returns error degenerate_route' is a useful guard. However, there is no explicit guidance on when to choose this over jt_compute_tco or jt_fractional_fit, which share cost-profile territory.

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

All Jet Tracker 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?