Can this product actually be returned? The merchant's exact clause, its URL and the date.
Answer one question: can this specific product actually be returned? BEST RESULTS: send the product page you already have as page_text (or page_html) along with product_url — your browser renders JavaScript and is not blocked by retailers, so this works on any store and is faster. Without it we fetch the page ourselves and reach the policy for about 1 in 3 US retailers (17 of 50 measured 2026-08-28; mostly Shopify and direct-to-consumer brands — large retailers and marketplaces block server-side reads). You get a verified verdict — YES / YES_WITH_CONDITIONS / NO / UNKNOWN — with the exact policy clause quoted verbatim, source URL, return window/deadline, fees and a confidence score. Never invents: returns UNKNOWN instead of guessing, and UNKNOWN is free.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| merchant | No | ||
| page_html | No | RECOMMENDED (alternative to page_text). Raw HTML of the same page. Slightly better than page_text: we can also read structured data (JSON-LD) from it. | |
| page_text | No | RECOMMENDED. Plain text of the product or returns page you already have open. We verify against this instead of fetching: works on any store, no blocking, no JavaScript problem, and faster. Still never invents: no verifiable clause -> UNKNOWN (free). | |
| product_url | Yes | The product page URL (http/https). | |
| seller_name | No | ||
| buyer_country | Yes | ISO 3166-1 alpha-2, e.g. 'US'. | |
| delivery_date | No | YYYY-MM-DD (optional; preferred for the deadline). | |
| purchase_date | No | YYYY-MM-DD (optional). | |
| item_condition | No | ||
| payment_signature | No | OPTIONAL. x402 payment authorization, base64 — the same envelope the PAYMENT-SIGNATURE header carries over HTTP. Use it to pay per call with no account and no signup. How: call once without it; if the free trial is exhausted you get the payment terms in structuredContent (x402Version, accepts[]); sign that authorization and call again with payment_signature set. Terms are also published at /.well-known/x402. UNKNOWN verdicts are never settled: the authorization simply expires unused. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so impressively. It explains the browser-rendering advantage, the fallback fetch success rate, the blocking behavior of large retailers, the policy-quoting behavior, the confidence score, and the rule 'never invents: returns UNKNOWN instead of guessing.' It also discloses that UNKNOWN is free and clarifies payment authorization behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is longer than average but front-loaded with the core purpose and best-results workflow. Each sentence contributes useful operational information, though a few phrases ('your browser renders JavaScript and is not blocked by retailers') could be trimmed without losing meaning. Overall it earns its length but is slightly dense.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is remarkably complete. It explains the verdict vocabulary, the exact policy clause quote, source URL, return window, fees, confidence score, fallback behavior, and the payment flow. An agent has enough context to invoke the tool correctly and interpret its result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 64%, so the description does not need to compensate for every parameter, but it still adds real meaning. It clarifies the relationship between page_text and page_html, explains why page_text is RECOMMENDED, and gives detailed operational context for payment_signature. However, some parameters like item_condition, reason, merchant, and seller_name receive no additional semantic guidance beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a precise question the tool answers: 'can this specific product actually be returned?' This states the verb, resource, and expected outcome unambiguously. It also names the concrete verdict values it produces, making the tool's function unmistakable even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage guidance: send page_text or page_html along with product_url for best results, and explains what happens when you don't ('Without it we fetch the page ourselves'). It does not compare against alternative tools, but no sibling tools exist, so the practical conditional guidance is strong and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
check_return1 field changedInput schema / properties / payment_signatureAdded value: +{
+ "description": "OPTIONAL. x402 payment authorization, base64 — the same envelope the PAYMENT-SIGNATURE header carries over HTTP. Use it to pay per call with no account and no signup. How: call once without it; if the free trial is exhausted you get the payment terms in structuredContent (x402Version, accepts[]); sign that authorization and call again with payment_signature set. Terms are also published at /.well-known/x402. UNKNOWN verdicts are never settled: the authorization simply expires unused.",
+ "type": "string"
+}check_return2 fields changedInput schema / properties / page_html / descriptionPrevious value: -"Optional: raw HTML of the page you already have. If provided, ReturnCheck verifies against it instead of fetching — best coverage, bypasses sites that block server-side reads. Still never invents: no verifiable clause -> UNKNOWN."New value: +"RECOMMENDED (alternative to page_text). Raw HTML of the same page. Slightly better than page_text: we can also read structured data (JSON-LD) from it."Input schema / properties / page_text / descriptionPrevious value: -"Optional: plain text of the page (alternative to page_html)."New value: +"RECOMMENDED. Plain text of the product or returns page you already have open. We verify against this instead of fetching: works on any store, no blocking, no JavaScript problem, and faster. Still never invents: no verifiable clause -> UNKNOWN (free)."check_return2 fields changedInput schema / properties / page_htmlAdded value: +{
+ "description": "Optional: raw HTML of the page you already have. If provided, ReturnCheck verifies against it instead of fetching — best coverage, bypasses sites that block server-side reads. Still never invents: no verifiable clause -> UNKNOWN.",
+ "type": "string"
+}Input schema / properties / page_textAdded value: +{
+ "description": "Optional: plain text of the page (alternative to page_html).",
+ "type": "string"
+}check_returnClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Official Japanese e-commerce rule evidence for mail-order advertising and return-policy disclosures.
Verify live product price, currency, stock, variants and published shipping evidence for AI agents.
Food verification for people and AI agents: evidence-backed verdicts, with sources and dates.
Delivered-price deals, cancel/refund paths, used-value comparisons, and compatibility checks.
Add one secure layer between your agents and this server.
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose as a return-eligibility checker is explicit and unambiguous.
check_return follows a clear verb_noun convention and is the only tool name, so there are no mixed styles or inconsistencies to penalize.
The tool directly serves the server's narrow purpose, but at one tool the surface feels thin and offers no auxiliary operations such as policy comparison or multi-product checks.
The tool fully covers the stated return-checking question: it accepts page context, falls back to server-side fetching, and returns a verified verdict with policy clause, source URL, window, fees, and confidence.