catalog

Search parts

search_parts

Read-only

Search the Satmarin catalog by part number, model or free text. Order: exact SKU (case and separators ignored), SKU prefix, then words found in the title or description in any order. A word that names an antenna model, such as v100NX, also matches parts fitted to that model. Use the model filter to restrict results to one model or series.

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	No	Exact brand slug, e.g. intellian.
`limit`	No	Default 10, maximum 25.
`model`	No	Antenna model or series, name or slug, e.g. v100NX or v-Series. Case and spacing are ignored; an unrecognised model returns an error.
`query`	Yes	Part number, model or free text.
`part_type`	No	Part type slug.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`match`	Yes
`total`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 14, 2026

changedInput schema / properties / brand / description

Previous value: -"Exact brand slug."New value: +"Exact brand slug, e.g. intellian."

changedInput schema / properties / model / description

Previous value: -"Antenna model slug."New value: +"Antenna model or series, name or slug, e.g. v100NX or v-Series. Case and spacing are ignored; an unrecognised model returns an error."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "match": {
+      "enum": [
+        "exact_sku",
+        "prefix",
+        "text"
+      ],
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "brand": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "compatible_models": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "eol": {
+            "type": "boolean"
+          },
+          "part_type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "price": {
+            "description": "EUR, ex works, VAT excluded. null when the part is discontinued or has no list price.",
+            "properties": {
+              "amount": {
+                "type": "number"
+              },
+              "basis": {
+                "enum": [
+                  "EXW"
+                ],
+                "type": "string"
+              },
+              "currency": {
+                "enum": [
+                  "EUR"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "amount",
+              "currency",
+              "basis"
+            ],
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "product_id": {
+            "type": "integer"
+          },
+          "sku": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "superseded_by": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "sku",
+          "product_id",
+          "title",
+          "brand",
+          "part_type",
+          "compatible_models",
+          "price",
+          "eol",
+          "superseded_by",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "results",
+    "total",
+    "match"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey readOnlyHint=true, covering the safety profile. The description goes beyond that by disclosing result ranking logic (exact SKU, prefix, then word order), case/separator handling for SKUs, and the non-obvious rule that antenna model words match parts fitted to that model. These are useful, non-schema-findable behavioral details.

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 four sentences long, with the core action front-loaded and no repeated information from the schema. Each sentence carries distinct value: the search purpose, the ranking, the model-word behavior, and the filter tip - so no waste.

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 100% schema description coverage, an existing output schema, and a readOnly annotation, the description supplies the only missing context: how search results are ordered and how the model filter should be used. No additional undocumented information is necessary to call the tool correctly.

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 value beyond the schema by explaining the relevance of the model parameter (restrict to model or series), and clarifies that the query accepts model words and how those match. This materially improves parameter understanding without being redundant.

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 states a specific verb (search), a specific resource (the Satmarin catalog), and enumerates the supported keys (part number, model, free text). It also specifies the exact ranking order of results, which makes it clearly distinguishable from non-search siblings like check_compatibility or get_quote.

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?

Clear context is provided: what you can search by, the order semantics, and a recommendation to use the model filter to scope results to a model or series. The description does not explicitly name alternative tools, but siblings are all non-search functions, so the when-to-use is essentially unambiguous.

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

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