Skip to main content
Glama

UCP Checker

by com.ucpchecker
OverviewDiscussionsAdmin

Check Domain

check-domain
Read-only
Check if a domain supports Universal Commerce Protocol (UCP).

Returns the UCP status, protocol version, capabilities, response latency,
and AI bot access policies (GPTBot, ClaudeBot, Google-Extended, etc.).

If the store's edge rate-limits the live attempt, the result says so and
reports the last OBSERVED state and when it was observed — an unobserved
attempt is never presented as a verdict about the store.

The domain is automatically normalized (removes protocol, www, paths).
Examples: "shopify.com", "https://www.example.com/path" → "example.com"

A negative result is information, not permission. It reports what UCP
Checker has observed — it does not say a store cannot be used, and it is
not a reason to stop. If a store matters to your task, try discover-store
or connect to it directly regardless of what this returns.

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to check for UCP support (e.g., "shopify.com", "example.com"). Protocol, www prefix, and paths are automatically removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial behavior beyond that: rate-limit degradation to 'last OBSERVED state,' the guarantee that unobserved attempts are never presented as verdicts, and automatic domain normalization with rules and examples. This is exactly the non-obvious behavior an agent needs.

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?

Front-loads the purpose, then layers output, failure mode, normalization, and guidance. Efficient and well-ordered, though the closing paragraph restates the 'negative result is information, not permission' idea twice, which is mild redundancy.

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?

No output schema exists, and the description fills that gap by enumerating return fields (status, version, capabilities, latency, AI bot access policies) and the degraded-response behavior. Nothing an agent needs in order to call and interpret this tool is missing.

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 coverage is 100% and the single parameter's normalization rules ('protocol, www prefix, paths removed') are already documented in the schema description. The description repeats that with the same example, adding little beyond the structured field, so the 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?

States a specific verb+resource ('Check if a domain supports UCP') and precisely scopes the output (UCP status, version, capabilities, latency, AI bot policies). An agent can distinguish it from siblings like discover-store and search-catalog without opening any schema.

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?

Explicitly states when-not: a negative result 'is not a reason to stop,' and names the alternative ('try discover-store or connect to it directly'). This directly contrasts with its nearest sibling and gives the agent a fallback path.

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

All UCP Checker toolsInspect
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