Jet Tracker

Search the aircraft catalog

jt_model_search

Read-onlyIdempotent

Search Jet Tracker aircraft models by text (manufacturer name such as "piper", model such as "meridian", both, or an ICAO type designator such as E55P or BE40) and category (jato = jet, helicoptero = helicopter, turboelice = turboprop, pistao = piston). Returns slug, familySlug, name, manufacturer, category, ICAO type, range, MTOW and production status, paginated with offset/nextOffset. The slug is the model id the other tools accept. Zero results is not proof of absence.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Máximo de modelos a devolver (1 a 20).
`query`	No	Termo de busca textual (fabricante, modelo, código ICAO). Opcional.
`offset`	No	Paginação: pule N modelos (nextOffset da página anterior).
`category`	No	Filtro por categoria.	qualquer

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"
+]

Changed9 schema fields changedSep 16, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Paginação: pule N modelos (nextOffset da página anterior).",
+  "maximum": 500,
+  "minimum": 0,
+  "type": "integer"
+}

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.3/5.0

Behavior4/5

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

Annotations already carry readOnly/idempotent/openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: pagination via offset/nextOffset, the returned field set, and the caveat "Zero results is not proof of absence" — a subtle but valuable caveat about incomplete matching.

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?

Three dense sentences, front-loaded with the primary search inputs before category, then pagination and return fields. Every clause carries information; it is slightly packed but never padded or redundant.

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?

An output schema exists, so return values needn't be enumerated, yet the description still names the key fields and adds the pagination contract and zero-result caveat. Combined with the annotation safety profile and full schema coverage, an agent has enough to call this correctly; only explicit sibling routing 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, but the description adds value by translating the Portuguese enum values (jato = jet, helicoptero = helicopter, turboelice = turboprop, pistao = piston) into English meaning, and by clarifying that offset continues from the previous page's nextOffset. This exceeds what the terse schema descriptions convey.

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 and resource ("Search Jet Tracker aircraft models") and enumerates the exact text inputs accepted — manufacturer, model, ICAO designator — plus a category filter. This clearly distinguishes it from siblings like jt_model_specs (spec detail) and jt_fleet_search (ownership/fleet), which an agent could otherwise confuse.

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?

Gives concrete usage patterns via query examples ("piper", "meridian", "E55P") and maps category enums to English meanings, which tells the agent how to construct calls. It also signals this is the entry point by noting "The slug is the model id the other tools accept", but never explicitly names an alternative tool or a when-not-to-use condition.

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?