Misfit Machine Store

Get Misfit machine product

get_product

Read-onlyIdempotent

Read-only detail retrieval for exactly one selected product. Call after search_catalog or lookup_catalog when full current price, availability, machine endpoint, and existing checkout-handoff metadata are needed. This does not create checkout, cart, order, payment, credential, or merchant state.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes	UCP caller metadata for capability negotiation only. This server is read-only.
`catalog`	Yes	Single-product detail. Minimal valid shape: {id:"product-id"}.

Output Schema

TableJSON Schema

Name	Required	Description
`ucp`	Yes
`product`	No	Current machine-consumable Misfit catalog product. Checkout URLs, when present, are handoff metadata only and do not authorize purchase.
`messages`	No

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 single-product detail response.",
+  "properties": {
+    "messages": {
+      "type": "array"
+    },
+    "product": {
+      "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"
+    },
+    "ucp": {
+      "additionalProperties": true,
+      "properties": {
+        "capabilities": {
+          "type": "object"
+        },
+        "status": {
+          "type": "string"
+        },
+        "version": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "version",
+        "status"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "ucp"
+  ],
+  "type": "object"
+}

Changed10 schema fields changedAug 21, 2026

changedInput schema / properties / catalog / description

Previous value: -"Single-product detail request."New value: +"Single-product detail. Minimal valid shape: {id:\"product-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 / id / description

Previous value: -"Exact product identifier returned by search_catalog or lookup_catalog."New value: +"Exact product ID returned by search_catalog or lookup_catalog."

changedInput schema / properties / catalog / properties / preferences / description

Previous value: -"Optional caller preferences relevant to product presentation; no purchase is performed."New value: +"Optional presentation preferences; no purchase occurs."

changedInput schema / properties / catalog / properties / selected / description

Previous value: -"Optional selected variant/options state from a prior catalog response; passed through to the backend."New value: +"Optional selected variant/options state from a prior catalog response."

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."

Changed11 schema fields changedAug 21, 2026

addedInput schema / properties / catalog / description
```
Added value: +"Single-product detail 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."
```

addedInput schema / properties / catalog / properties / id / description

Added value: +"Exact product identifier returned by search_catalog or lookup_catalog."

addedInput schema / properties / catalog / properties / preferences / description

Added value: +"Optional caller preferences relevant to product presentation; no purchase is performed."

addedInput schema / properties / catalog / properties / selected / description

Added value: +"Optional selected variant/options state from a prior catalog response; passed through to the backend."

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?

Annotations already declare readOnlyHint=true and destructiveHint=false; description adds the specific non-actions (does not create checkout, cart, order, etc.) and frames it as 'read-only detail retrieval', reinforcing the idempotentHint. It doesn't mention rate limits or auth beyond the UCP profile mention which is in schema, but adds enough context beyond annotations.

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 a single, front-loaded paragraph (approximately 60 words) that states the purpose, the when-to-use, and the boundary of what it does not do. Every sentence adds value and there is no redundancy with the schema.

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 there is an output schema and the annotations disclose read-only/idempotent behavior, the description covers the essential prerequisites (requires 'meta.ucp-agent.profile', 'catalog.id') implicitly via schema, and explicitly states the side-effect-free guarantee. It doesn't explain error conditions or rate limits, but those are not required for high completeness. The missing negative guidance on when NOT to call it (e.g., for multi-product or mutation) is implied by 'exactly one selected product' and the non-actions.

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 has thorough parameter descriptions (100% coverage), including the purpose of each field and clarifications like 'no purchase occurs' and 'never authorizes billing.' The tool description adds little beyond pointing to the schema's 'exactly one selected product' requirement and id source. Given the high schema coverage, the description doesn't need to add much; 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?

Description states a specific verb ('read-only detail retrieval') and resource ('exactly one selected product'), and explicitly distinguishes from sibling tools by naming them and the sequencing ('Call after search_catalog or lookup_catalog'). It also enumerates what it does NOT do (create cart, order, etc.), making its scope unmistakable.

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?

Provides explicit when to use: after search_catalog or lookup_catalog, when full current price, availability, machine endpoint, and checkout-handoff metadata are needed. Also specifies a clear when-not by listing side-effects it does not produce (create checkout, cart, order, payment, credential, merchant state).

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?