Misfit Machine Store

Lookup Misfit machine products

lookup_catalog

Read-onlyIdempotent

Read-only identifier lookup. Call this when you already have one or more product, variant, SKU, or handle IDs and need current price, availability, or machine endpoint data. No purchase or mutation occurs. Use search_catalog if IDs are unknown; use get_product for full detail on one selected item.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes	UCP caller metadata for capability negotiation only. This server is read-only.
`catalog`	Yes	Identifier lookup. Minimal valid shape: {ids:["known-id"]}.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ucp`	Yes
`messages`	No
`products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "UCP identifier lookup response. Missing identifiers may appear in messages.",
+  "properties": {
+    "messages": {
+      "type": "array"
+    },
+    "products": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Current machine-consumable Misfit catalog product. Checkout URLs, when present, are handoff metadata only and do not authorize purchase.",
+        "properties": {
+          "categories": {
+            "type": "array"
+          },
+          "description": {
+            "type": "object"
+          },
+          "handle": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "metadata": {
+            "type": "object"
+          },
+          "price_range": {
+            "type": "object"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "variants": {
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ucp": {
+      "additionalProperties": true,
+      "properties": {
+        "capabilities": {
+          "type": "object"
+        },
+        "status": {
+          "type": "string"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "version",
+        "status"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "ucp",
+    "products"
+  ],
+  "type": "object"
+}

Changed10 schema fields changedAug 21, 2026

changedInput schema / properties / catalog / description

Previous value: -"Identifier-based catalog lookup request."New value: +"Identifier lookup. Minimal valid shape: {ids:[\"known-id\"]}."

changedInput schema / properties / catalog / properties / attribution / description

Previous value: -"Optional source/channel attribution metadata for discovery analytics."New value: +"Optional discovery attribution. Suggested fields: source (registry/client/platform), channel, campaign, referrer. Attribution is analytics metadata only and never authorizes billing."

changedInput schema / properties / catalog / properties / context / description

Previous value: -"Optional UCP caller context; passed through read-only."New value: +"Optional UCP caller context."

changedInput schema / properties / catalog / properties / filters / description

Previous value: -"Optional backend-supported filters applied to the lookup."New value: +"Optional backend-supported filters."

changedInput schema / properties / catalog / properties / ids / description

Previous value: -"One to 100 known catalog identifiers to resolve."New value: +"One to 100 known identifiers."

changedInput schema / properties / catalog / properties / ids / items / description

Previous value: -"Known product, variant, SKU, or handle identifier."New value: +"Exact product, variant, SKU, or handle identifier."

changedInput schema / properties / catalog / properties / signals / description

Previous value: -"Optional machine-selection signals; passed through read-only."New value: +"Optional machine-selection signals."

changedInput schema / properties / meta / description

Previous value: -"UCP caller metadata used only for capability negotiation; this read-only server does not mutate carts, orders, payments, credentials, or merchant data."New value: +"UCP caller metadata for capability negotiation only. This server is read-only."

changedInput schema / properties / meta / properties / ucp-agent / description

Previous value: -"Calling UCP agent identity/profile metadata."New value: +"Calling UCP agent metadata."

changedInput schema / properties / meta / properties / ucp-agent / properties / profile / description

Previous value: -"Absolute URI of the caller's UCP profile document. Required on every catalog tool call."New value: +"Absolute URI of the caller's UCP profile. Required on every call."

Changed10 schema fields changedAug 21, 2026

addedInput schema / properties / catalog / description

Added value: +"Identifier-based catalog lookup request."

addedInput schema / properties / catalog / properties / attribution / description

Added value: +"Optional source/channel attribution metadata for discovery analytics."

addedInput schema / properties / catalog / properties / context / description
```
Added value: +"Optional UCP caller context; passed through read-only."
```
addedInput schema / properties / catalog / properties / filters / description
```
Added value: +"Optional backend-supported filters applied to the lookup."
```
addedInput schema / properties / catalog / properties / ids / description
```
Added value: +"One to 100 known catalog identifiers to resolve."
```
addedInput schema / properties / catalog / properties / ids / items / description
```
Added value: +"Known product, variant, SKU, or handle identifier."
```

addedInput schema / properties / catalog / properties / signals / description

Added value: +"Optional machine-selection signals; passed through read-only."

addedInput schema / properties / meta / description

Added value: +"UCP caller metadata used only for capability negotiation; this read-only server does not mutate carts, orders, payments, credentials, or merchant data."

addedInput schema / properties / meta / properties / ucp-agent / description
```
Added value: +"Calling UCP agent identity/profile metadata."
```

addedInput schema / properties / meta / properties / ucp-agent / properties / profile / description

Added value: +"Absolute URI of the caller's UCP profile document. Required on every catalog tool call."

First observedAug 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces these with 'Read-only' and 'No purchase or mutation occurs,' which adds a small amount of context beyond the annotations. However, it does not mention potential errors, rate limits, or other side effects that might affect caller behavior.

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 two sentences long, starts with the core purpose ('Read-only identifier lookup'), and packs all necessary guidance without fluff. It front-loads the action and resource, then provides usage and alternatives in a compact, scannable manner.

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?

For a simple identifier lookup tool, the description provides sufficient context: it explains what data is returned (price, availability, machine endpoint data), when to use it, and how it differs from siblings. It does not describe the output schema, but the presence of an output schema (as indicated in context) means that is not required. The description is slightly generic about optional parameters but still gives a complete picture for an agent.

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 input schema provides descriptions for all parameters (ids, context, filters, signals, attribution), achieving 100% coverage. The tool description does not add much beyond what the schema states; it repeats the types of identifiers and mentions the return intent, but does not clarify the meaning or purpose of the optional parameters. Since coverage is high, a baseline of 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?

The description clearly states the verb ('lookup') and resource ('catalog'), and specifies the exact use case: retrieving current price, availability, or machine endpoint data for known product, variant, SKU, or handle IDs. It also names sibling tools directly, distinguishing itself from search_catalog (unknown IDs) and get_product (single item full detail).

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool: 'Call this when you already have one or more product, variant, SKU, or handle IDs and need current price, availability, or machine endpoint data.' It also gives clear alternative instructions: 'Use search_catalog if IDs are unknown; use get_product for full detail on one selected item.' This leaves no ambiguity.

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

All Misfit Machine Store 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?