Facet UCP Shopping

discover_businesses

Find businesses in the Facet Universal Business Index that an agent can transact with. Returns featured (claimed merchants with a live terminal_url — point your catalog and checkout calls there) and results (the wider directory). Use this first when you do not already know which merchant to talk to. REQUIRES IDENTITY: send a Facet KYA as Authorization: Bearer <kya> on the MCP request. A KYA is an ES256 JWT from Facet's default issuer https://issuer.facet.llc (or another issuer this Terminal trusts — see KYA-Issuers in its /.well-known/agents.txt). Calling without one returns 401 with a signup link.

Input Schema

TableJSON Schema

Name	Required	Description
`near`	No	Optional geographic center to rank by proximity.
`limit`	No	Max matches to return. Default 10, cap 50.
`query`	No	Free-text query, e.g. "flowers" or "makeup brushes".
`radius_km`	No	Search radius around `near`, km. Default 25.

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Clearly discloses authentication requirement (KYA token) and return structure (featured and results). Does not mention rate limits or pagination, but is transparent about critical behavioral trait (auth).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is three sentences plus a detailed auth paragraph. Front-loaded with main purpose. Some minor verbosity in auth section but overall concise 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 no output schema and 4 parameters, the description explains return values and auth. However, lacks guidance on using 'featured' field in subsequent calls. Mostly complete but could be slightly more actionable.

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 100%, so the schema already documents each parameter. The description does not add significant new meaning beyond what is in the schema. 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?

Clear verb 'Find businesses' and specific resource 'in the Facet Universal Business Index that an agent can transact with'. Distinguishes between 'featured' and 'results', giving precise scope. Differentiates from sibling tools like get_order or search_catalog.

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

Usage Guidelines4/5

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

Explicitly tells when to use ('Use this first when you do not already know which merchant to talk to'). Provides pre-requisite: requires a Facet KYA token. Does not explicitly state when not to use, but the context is clear.

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

All Facet UCP Shopping tools Inspect

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

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.

Resources

Need Help?