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 (jet, turboprop, helicopter, piston, the same words as jt_fleet_search). 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

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	jet, turboprop, helicopter, piston or any (the Portuguese jato, turboelice, helicoptero, pistao, qualquer also work).	any

Output 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.

Changed3 schema fields changedOct 28, 2026

changedInput schema / properties / category / default
```
Previous value: -"qualquer"New value: +"any"
```

changedInput schema / properties / category / description

Previous value: -"Filtro por categoria."New value: +"jet, turboprop, helicopter, piston or any (the Portuguese jato, turboelice, helicoptero, pistao, qualquer also work)."

changedInput schema / properties / category / enum

Previous value: -[
-  "jato",
-  "helicoptero",
-  "turboelice",
-  "pistao",
-  "qualquer"
-]New value: +[
+  "jet",
+  "turboprop",
+  "helicopter",
+  "piston",
+  "any",
+  "jato",
+  "turboelice",
+  "helicoptero",
+  "pistao",
+  "qualquer"
+]

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds the pagination contract (offset/nextOffset) and the coverage caveat that zero results doesn't prove absence, which is real added context. It does not discuss rate limits or result ordering, so it earns above-baseline but not rich.

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 search axes, then the return shape, then the slug/pagination guidance. The enumerated return-field list overlaps what the output schema already provides, which is minor waste, but nothing else is padding.

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?

For a zero-required-parameter, 4-param search tool with a dedicated output schema and full annotation coverage, the description covers scope, vocabulary, return identity (slug) and the caveat about empty results. An agent has everything needed to call it correctly and interpret an empty response.

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 limit, query, offset and category, including the enum values. The description's value-add is concrete query examples ("piper", "meridian", E55P, BE40) that the schema lacks, but the category and pagination explanation largely restates the schema. Baseline 3 is appropriate.

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 (search) and resource (Jet Tracker aircraft models) and enumerates the two axes of filtering (text and category) with concrete examples. An agent can distinguish this catalog-search tool from jt_fleet_search or jt_global_fleet_search without opening a schema.

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?

Explicitly notes the category vocabulary matches jt_fleet_search and that the returned slug is the model id other tools accept, which tells the agent how to chain calls. It also warns that zero results is not proof of absence. It stops short of naming a sibling to use instead when searching fleets vs models, so a 4 rather than a 5.

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?