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, manifest 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

TableJSON 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.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, but the description adds substantial context beyond that: edge rate-limiting behavior, the distinction between OBSERVED and unobserved verdicts, automatic domain normalization, and the caveat that a negative result is not permission. These details are not redundant with annotations and give the agent a full picture of behavior and caveats.

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 organized in short, focused paragraphs with front-loaded purpose and returns. Each sentences contributes either a key fact, a caveat, or a routing instruction. Despite length, it's efficient and well-structured; no filler.

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?

With no output schema, the description fully explains what the tool returns (status, manifest version, capabilities, latency, AI bot policies) and how to interpret edge cases like rate limiting. It also covers normalization and the philosophical stance on negative results. For a single-parameter read-only tool, nothing necessary for correct invocation or interpretation is missing.

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

Parameters4/5

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

The schema describes the domain parameter with examples and normalization rules, achieving 100% coverage. The description reinforces this with the same normalization explanation and additional examples ('shopify.com', 'https://www.example.com/path' → 'example.com'), which add minor value beyond the schema but don't introduce new parameter semantics.

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 states a specific verb+resource: 'Check if a domain supports Universal Commerce Protocol (UCP).' It enumerates the returned data (UCP status, manifest version, capabilities, latency, AI bot policies) and distinguishes itself from siblings by name (discover-store) as an alternative for store discovery, making its role unambiguous.

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?

Explicit guidance is provided: 'A negative result is information, not permission... 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.' This gives a clear when-to-use/use-alternative rule and even explains how to interpret negative results, leaving no ambiguity.

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