catalog

Resolve supersession

resolve_supersession

Read-only

Is a part discontinued, and what replaces it? Give sku or product_id. Follows the replacement chain to the latest live product: successors lists the live replacements, supersedes lists the parts this one replaced.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	No	Part number. Give this or product_id.
`product_id`	No	Catalog product id. Give this or sku.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`eol`	Yes
`sku`	Yes
`successors`	Yes
`supersedes`	Yes
`no_replacement`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 14, 2026

addedInput schema / properties / product_id / description
```
Added value: +"Catalog product id. Give this or sku."
```

addedInput schema / properties / sku / description

Added value: +"Part number. Give this or product_id."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "eol": {
+      "type": "boolean"
+    },
+    "no_replacement": {
+      "type": "boolean"
+    },
+    "sku": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "successors": {
+      "items": {
+        "properties": {
+          "sku": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "sku",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "supersedes": {
+      "items": {
+        "properties": {
+          "sku": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "sku",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sku",
+    "eol",
+    "successors",
+    "supersedes",
+    "no_replacement"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description adds value beyond the read-only annotation by explaining the replacement chain behavior (follows chain to latest live product, lists successors and supersedes). This is useful context not provided by the schema. However, it doesn't disclose details like whether the tool returns partial chains or handles multiple inputs, but the annotation covers safety, so a 3 is appropriate.

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 efficient with minimal waste, clearly stating the purpose and the output fields (successors/supersedes) upfront. The key information is front-loaded, and every sentence earns its place.

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?

Given the tool's moderate complexity (2 parameters, one optional, with output schema), the description provides enough context to call it correctly. It explains the input selection and the replacement chain output. The presence of an output schema reduces the need to describe return values, so a 4 is justified.

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 coverage is 100%, so both parameters are already documented in the schema. The description reinforces that you provide either sku or product_id, but doesn't add new details such as preferred input or precedence. Baseline 3 is correct given the high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool resolves part discontinuation and provides successors, with a specific resource (parts) and action (resolve supersession). It distinguishes from siblings like search_parts (which searches for parts) and get_quote (pricing) by focusing on lifecycle and replacement chain, though it doesn't explicitly name alternatives.

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 provides clear context for when to use this tool: when a part is discontinued and you need to find replacements, and it implies the replacement chain behavior. However, it doesn't explicitly state when not to use it or mention alternatives, so guidance is good but not fully explicit.

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?