Skip to main content
Glama

catalog

by net.fsaircraft
OverviewDiscussionsAdmin

Search MSFS add-ons

search_addons
Read-onlyIdempotent

Search the fsaircraft.net catalog of payware Microsoft Flight Simulator add-ons (aircraft, scenery, liveries, utilities) across every tracked store. Returns the cheapest live offer for each add-on with its discount and MSFS 2020/2024 compatibility as declared by the selling store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text: title, developer, ICAO code or aircraft type
simNoOnly add-ons declared compatible with this simulator
limitNo
storeNoStore slug, e.g. 'simmarket' — see list_stores
on_saleNoOnly add-ons currently below their recorded high
categoryNoCategory slug, e.g. 'aircraft', 'scenery', 'livery', 'utility'
max_price_eurNoInclusive ceiling on the known VAT-excluded price, in euros

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYes
countYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / max_price_eur / description
      Previous value: -"Inclusive ceiling on the cheapest offer, in euros"New value: +"Inclusive ceiling on the known VAT-excluded price, in euros"
    • addedOutput schema / properties / results / items / properties / net_price_eur_cents
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / results / items / properties / tax_status
      Added value: +{
+  "enum": [
+    "included",
+    "excluded",
+    "unknown"
+  ],
+  "type": "string"
+}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
-  "slug",
-  "title",
-  "developer",
-  "category",
-  "sims",
-  "price_cents",
-  "currency",
-  "price_eur_cents",
-  "net_price_cents",
-  "store",
-  "discount_pct",
-  "was_price_cents",
-  "sale_ends_at",
-  "offer_count",
-  "rating",
-  "url"
-]New value: +[
+  "slug",
+  "title",
+  "developer",
+  "category",
+  "sims",
+  "price_cents",
+  "currency",
+  "price_eur_cents",
+  "net_price_cents",
+  "net_price_eur_cents",
+  "tax_status",
+  "store",
+  "discount_pct",
+  "was_price_cents",
+  "sale_ends_at",
+  "offer_count",
+  "rating",
+  "url"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish a read-only, idempotent, non-destructive profile, so the description only needs to add context beyond that. It discloses that results are 'cheapest live offer' with discount and store-declared MSFS compatibility, which are useful behavioral caveats. No 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?

Two sentences that front-load the search scope and then explain the return value. Every clause adds information, with no repetition of schema content or filler.

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 seven optional parameters, high schema coverage, an output schema, and safe read-only annotations, the description provides enough context for an agent to call the tool correctly. It covers scope, result meaning, and the compatibility caveat.

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 86%, and parameters like q, sim, limit, store, on_sale, category, and max_price_eur already carry their own descriptions. The main description adds little parameter-level detail, so the baseline of 3 applies.

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 the fsaircraft.net catalog of payware MSFS add-ons across every tracked store. It also clarifies the result semantics (cheapest live offer, discount, compatibility), which distinguishes it from generic search/list siblings.

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 to use the tool: querying the catalog across all tracked stores and surfacing the cheapest live offer. It does not explicitly name alternatives or exclusion conditions, so it stops short of full routing guidance.

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

All catalog toolsInspect
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