AirShelf Catalog

Explain how a record was built

explain_product

Read-only

Explain the evidence behind a catalog row. Returns stored processing stages when available and always returns a golden-record field summary with source coverage. A field's evidence_sha256 is the SHA-256 of the source document AirShelf archived when it extracted that claim. A caller holding the same bytes can compare the hash to check that the cited document has not changed. AirShelf does not serve those archived bytes, and the hash does not promise they remain retrievable. record.scraped_at is the catalog row's scrape time, not a per-claim evidence capture time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Composite slug to explain

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	No
`note`	No
`slug`	No
`count`	No
`trace`	No
`record`	No
`category`	No
`trace_status`	No
`canonical_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 5, 2026
- addedInput schema / properties / slug / minLength
```
Added value: +1
```
- addedOutput schema / properties / canonical_name
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / record
```
Added value: +{}
```
- addedOutput schema / properties / trace_status
```
Added value: +{
+  "enum": [
+    "available",
+    "not_recorded"
+  ],
+  "type": "string"
+}
```
Changed1 schema field changedJul 13, 2026
- addedOutput schema / properties / trace
```
Added value: +{}
```

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "sku": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses the meaning of evidence_sha256, clarifies that AirShelf does not serve archived bytes, and distinguishes record.scraped_at from per-claim capture time. These are significant behavioral details that prevent misinterpretation.

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, each adding a distinct piece of information: purpose, output, hash semantics, and timestamp clarification. It is front-loaded with the core purpose and avoids redundancy, making it efficient and well-structured.

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 output schema exists, the description does not need to list return fields, but it adds critical clarifications about hash usage and timestamp interpretation. It covers the key behavioral aspects thoroughly, though it omits potential error conditions, which is minor.

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?

The schema provides a description for the single parameter slug ('Composite slug to explain'), so coverage is 100%. The description does not add further parameter-specific meaning beyond referring to the catalog row, so the baseline 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?

The description clearly states the tool explains the evidence behind a catalog row, and specifies it returns processing stages and a golden-record field summary with source coverage. This distinguishes it from sibling tools like get_product or compare_products, which focus on retrieval or comparison rather than provenance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when evidence or provenance is needed, but it does not explicitly compare with alternatives or state when not to use it. It gives context on what the tool returns, but no direct routing guidance, so it is adequate but not explicit.

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

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