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.

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

A3.8/5.0

Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds pagination behavior and a zero-results caveat. However, 'Zero results is not proof of absence' directly contradicts openWorldHint=false, which signals a closed world where absence can be treated as definitive; this is an annotation contradiction.

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?

Four dense sentences with the core search behavior first, then return fields, slug hand-off, and the zero-results caveat. Every sentence earns its place and there is no filler.

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?

The description covers query semantics, category values, return fields, pagination, and model-id hand-off, which is complete for a read-only search tool with full parameter coverage and an output schema. The open-world contradiction is the only notable completeness flaw.

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. The description adds concrete query examples (piper, meridian, E55P/BE40), maps the Portuguese category enum to English meanings, and clarifies offset/nextOffset pagination, going beyond the raw schema.

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 first sentence names a specific action ('Search Jet Tracker aircraft models') and clearly delimits the resource (model catalog) and query axes (text and category). It also ties the returned slug to 'the model id the other tools accept', helping distinguish this search tool from sibling lookup and fleet 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?

It gives clear usage context: search by manufacturer/model/ICAO text and category, with pagination and the returned slug used for subsequent tool calls. It never names alternatives like jt_aircraft_lookup or jt_model_specs nor states when not to use them, so it stops short of a full routing guide.

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?