Jet Tracker

Total cost of ownership (comparator)

jt_compute_tco

Read-onlyIdempotent

Total cost of ownership across FIVE operating models (own, fractional, charter, jetcard, invest + charter) for a model with a full cost profile, given hours per year, horizon and opportunity rate: average annual and hourly cost, undiscounted horizon total, NPV and the year-by-year cashflows of every scenario (sign convention: outflows negative), plus assumptions (variable per hour and fixed per year from the SAME canonical cost engine as jt_model_specs, costModelVersion, fractional hours included). Accepts the catalog slug or any alias (phenom-300, embraer-phenom-300e, hawker 400xp); comparadorProfiles in jt_model_search lists the five profiles. Values in USD; Brazilian opportunity rate (CDI/Selic) by default.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Modelo com calculadora completa: slug de catálogo (phenom-100, embraer-phenom-300, beechcraft-hawker-400xp, leonardo-aw109-power, airbus-h125), slug do perfil (embraer-phenom-100, leonardo-aw109), alias, família ou nome. A resposta diz em model qual perfil foi usado.
`horizonYears`	No	Horizonte da comparação em anos: 1, 3, 5 ou 10. Default 5.
`hoursPerYear`	Yes	Horas voadas por ano (10-600, limite do comparador).
`opportunityRatePct`	No	Taxa de oportunidade do capital (CDI/Selic). Default 12% BR 2026.

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.

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: slug de catálogo (phenom-100, embraer-phenom-300, beechcraft-hawker-400xp, leonardo-aw109-power, airbus-h125), slug do perfil (embraer-phenom-100, leonardo-aw109), alias, família ou nome. A resposta diz em model qual perfil foi usado."

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

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool as readOnly, idempotent, and non-destructive, and the description adds substantial behavioral detail: sign convention for cashflows, output components (average annual/hourly cost, NPV, year-by-year cashflows), assumptions sourced from the same engine as jt_model_specs, fractional hours included, currency, and default Brazilian opportunity rate. No contradiction with annotations.

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?

The description is three dense sentences with no filler. It front-loads the core purpose and outputs, then packs assumptions, aliases, and currency/default details efficiently. Every clause earns its place.

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?

Given the tool's complexity, the description covers inputs, outputs, assumptions, sign convention, currency, defaults, and alias resolution. An output schema exists for return shape, so the description does not need to repeat return fields. Nothing essential for selecting or invoking the tool correctly 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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by giving concrete alias examples (phenom-300, embraer-phenom-300e, hawker 400xp), noting that comparadorProfiles in jt_model_search lists the five profiles, and clarifying that the model must have a full cost profile.

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?

The description opens with a specific verb and resource: 'Total cost of ownership across FIVE operating models' and enumerates exactly what is computed. It also distinguishes itself from siblings by naming jt_model_specs as the canonical cost engine and jt_model_search as the source for the five profiles, so an agent can tell it apart from related lookup/spec 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?

The description gives clear context for when this tool is appropriate: it requires a model with a full cost profile and accepts catalog slugs or aliases, with jt_model_search listing the five profiles. It does not explicitly state when not to use it or name direct alternatives, but the references to jt_model_specs and jt_model_search provide enough routing guidance.

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?