Skip to main content
Glama

Misfit Machine Store

by io.github.MisfitMEdiAhouse

Server Details

UCP-compatible machine catalog for paid Misfit agent APIs and MCP services.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Available Tools

3 tools
get_productGet Misfit machine productA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
metaYesUCP caller metadata for capability negotiation only. This server is read-only.
catalogYesSingle-product detail. Minimal valid shape: {id:"product-id"}.

Output Schema

ParametersJSON Schema
NameRequiredDescription
ucpYes
productNoCurrent machine-consumable Misfit catalog product. Checkout URLs, when present, are handoff metadata only and do not authorize purchase.
messagesNo

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.

lookup_catalogLookup Misfit machine productsA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
metaYesUCP caller metadata for capability negotiation only. This server is read-only.
catalogYesIdentifier lookup. Minimal valid shape: {ids:["known-id"]}.

Output Schema

ParametersJSON Schema
NameRequiredDescription
ucpYes
messagesNo
productsYes

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.

search_catalogSearch Misfit machine productsA
Read-onlyIdempotent
Inspect

Read-only product discovery. Call this first when you do not know a product ID. Returns matching machine-consumable products with current price, availability, and machine endpoint metadata. No cart, checkout, order, payment, credential, or merchant mutation occurs. Use lookup_catalog when IDs are known; use get_product after selecting one product.

ParametersJSON Schema
NameRequiredDescriptionDefault
metaYesUCP caller metadata for capability negotiation only. This server is read-only.
catalogYesSearch request. Minimal valid shape: {query:"change monitoring"}. Query may be omitted for default discovery.

Output Schema

ParametersJSON Schema
NameRequiredDescription
ucpYes
messagesNo
productsYes
paginationNo

TDQS

A5/5.0
Behavior5/5

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

Explicitly states it is read-only, returns matching products with price, availability, and endpoint metadata; clarifies no cart, checkout, order, payment, credential, or merchant mutation occurs. Annotations (readOnly=true, idempotent=true, destructive=false) align with the description, so no contradiction. This is a model of behavioral transparency.

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 concise but informative, using clear bullet-style clauses. The schema is well-structured with nested objects and clear descriptions. The additional text explaining when to call and what does not happen is efficient and not verbose.

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?

The description provides full context: it states read-only semantics, what the tool returns, what it doesn't do, and how it fits into a workflow (use lookup_catalog when IDs are known, get_product after selecting). It covers usage scenarios shortages (like knowing product ID) and highlights non-mutations. The schema explains required fields and optional fields. This is highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides detailed descriptions for each parameter: meta explains it's for capability negotiation and is read-only; catalog describes its role as a search request with query, context, filters, signals, and pagination. The 'query' parameter has examples and pagination has min/max and descriptions. The schema description coverage is 100% per the metadata, and the description provides additional examples and clarifies optional fields. Parameters are well-documented.

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?

Title and description clearly state the tool's purpose: searching Misfit machine products. It explicitly mentions it is read-only product discovery and says to call it first when the product ID is unknown, with clear next steps (lookup_catalog, get_product).

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 strong usage context: call this when product ID is unknown, use lookup_catalog when IDs are known, and use get_product after selecting a product. Also explains the purpose of the tool in the discovery flow, making usage guidelines excellent.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updates
    • Changedget_product1 field changed
      • 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"
+}
    • Changedlookup_catalog1 field changed
      • 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"
+}
    • Changedsearch_catalog3 fields changed
      • addedInput schema / properties / catalog / properties / pagination / additionalProperties
        Added value: +true
      • addedInput schema / properties / catalog / properties / pagination / properties
        Added value: +{
+  "cursor": {
+    "description": "Opaque cursor returned by a prior search response.",
+    "type": "string"
+  },
+  "limit": {
+    "description": "Maximum products to return; backend default is 10.",
+    "maximum": 50,
+    "minimum": 1,
+    "type": "integer"
+  }
+}
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "UCP catalog search response. Products are read-only discovery results.",
+  "properties": {
+    "messages": {
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": true,
+      "properties": {
+        "cursor": {
+          "type": "string"
+        },
+        "has_next_page": {
+          "type": "boolean"
+        },
+        "total_count": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "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"
+}
  2. 3 tool updates
    • Changedget_product10 fields changed
      • 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."
    • Changedlookup_catalog10 fields changed
      • 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."
    • Changedsearch_catalog10 fields changed
      • changedInput schema / properties / catalog / description
        Previous value: -"Catalog search request."New value: +"Search request. Minimal valid shape: {query:\"change monitoring\"}. Query may be omitted for default discovery."
      • changedInput schema / properties / catalog / properties / attribution / description
        Previous value: -"Optional source/channel attribution metadata used for discovery analytics, not billing authorization."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 context supplied by the caller; passed through to the catalog service."New value: +"Optional UCP caller context."
      • changedInput schema / properties / catalog / properties / filters / description
        Previous value: -"Optional catalog filters supported by the UCP backend."New value: +"Optional backend-supported filters."
      • changedInput schema / properties / catalog / properties / pagination / description
        Previous value: -"Optional pagination controls supported by the UCP backend."New value: +"Optional pagination controls."
      • changedInput schema / properties / catalog / properties / query / description
        Previous value: -"Natural-language or keyword query such as 'A2A audit', 'change monitoring', or 'machine commerce'. Empty/omitted query may return the default discoverable catalog."New value: +"Natural-language or keyword query, e.g. 'A2A audit', 'change monitoring', or 'machine commerce'."
      • changedInput schema / properties / catalog / properties / signals / description
        Previous value: -"Optional machine-selection signals supplied by the caller; passed through without side effects."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."
  3. 3 tool updates
    • Changedget_product11 fields changed
      • 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."
    • Changedlookup_catalog10 fields changed
      • 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."
    • Changedsearch_catalog10 fields changed
      • addedInput schema / properties / catalog / description
        Added value: +"Catalog search request."
      • addedInput schema / properties / catalog / properties / attribution / description
        Added value: +"Optional source/channel attribution metadata used for discovery analytics, not billing authorization."
      • addedInput schema / properties / catalog / properties / context / description
        Added value: +"Optional UCP context supplied by the caller; passed through to the catalog service."
      • addedInput schema / properties / catalog / properties / filters / description
        Added value: +"Optional catalog filters supported by the UCP backend."
      • addedInput schema / properties / catalog / properties / pagination / description
        Added value: +"Optional pagination controls supported by the UCP backend."
      • addedInput schema / properties / catalog / properties / query / description
        Added value: +"Natural-language or keyword query such as 'A2A audit', 'change monitoring', or 'machine commerce'. Empty/omitted query may return the default discoverable catalog."
      • addedInput schema / properties / catalog / properties / signals / description
        Added value: +"Optional machine-selection signals supplied by the caller; passed through without side effects."
      • 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."
  4. 3 tool updates
    • First observedget_product
    • First observedlookup_catalog
    • First observedsearch_catalog

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • verdigraph

    viridis-security
    A
    license
    Not graded
    quality
    B
    maintenance
    Paid hosted MCP for agent-to-agent compute routing and brain-builder workflows. OAuth 2.1 + PKCE auth, Stripe prepaid USD credits, 29 tools (10 free, 19 metered). 25% of net revenue funds verified conservation via a public auditable ledger. SEP-1960 manifest and SEP-1649 server card published.
    1
    MIT

  • Lingshu Gate

    zhigege666
    A
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted MCP gateway and control plane that aggregates and manages MCP servers and tools, providing unified access, a web console, access control, invocation auditing, and integrated build/deploy workflows.
    Apache 2.0
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

The three tools have distinct use cases (discovery, known IDs, single full detail), but the verbose and overlapping descriptions may cause some confusion between lookup_catalog and get_product.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (search, lookup, get) with clear nouns, making them predictable and coherent.

Tool Count5/5

With only three read-only catalog operations, the count is well-scoped for the server's stated purpose of product retrieval without mutation.

Completeness5/5

For a read-only catalog, the surface covers the essential operations: searching by unknown criteria, looking up by known IDs, and retrieving full details for a single product. No critical gaps are apparent.

Resources