lookup_catalog
Look up one or more products or variants by identifier (batch).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| catalog | Yes |
Facet UCP Shopping
by llc.facet
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully convey behavioral traits. It states 'by identifier (batch)' but does not disclose outcomes for missing IDs, rate limits, or that it is a read-only operation. Key behaviors are omitted.
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?
A single, clear sentence with no unnecessary words. Information is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (batch lookup by ID), the description covers the core action but lacks details on error handling, return format, and whether the operation is read-only. With no output schema, these gaps reduce completeness.
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 description coverage is 0%, so the description must compensate. It adds the context that identifiers are used for batch lookup, but does not elaborate on the format of IDs or the nested structure. Some value added, but insufficient for full clarity.
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 looks up products or variants by identifier in batch, distinguishing it from sibling tools like search_catalog (query-based) and get_product (single item).
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 identifiers are available, but lacks explicit guidance on when to use this tool versus alternatives like search_catalog or get_product. No exclusions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation3/5
Most tools map to a distinct lifecycle step, and the detailed descriptions separate discovery, cart, checkout, payment, order, and wishlist concerns well. However, get_product and lookup_catalog are largely the same lookup by identifier, discover_products and search_catalog overlap across scope, and update_checkout is actually a read-only no-op.
Naming Consistency4/5
The set overwhelmingly follows a verb_noun pattern: create_cart, get_checkout, cancel_checkout, complete_checkout, search_catalog. Minor deviations are the wishlist_* resource-first subgroup and the misleading update_checkout, which does not perform an update.
Tool Count3/5
At 23 tools, this sits at the heavy end of the range, though the broad commerce lifecycle does justify substantial surface area. The count is inflated by redundant product lookup tools and a no-op update_checkout, so a more trimmed set in the low-to-mid teens would be healthier.
Completeness4/5
The server covers the full shopper lifecycle well: discovery, product lookup, cart, checkout, payment, order placement, order read, refunds, and wishlist. Gaps are minor and workable, such as update_checkout not actually supporting updates and no explicit order-cancellation path once a checkout is complete.