mcp-livedatapro

getMerchantReturnPolicy

Parse merchant return windows, restocking fees, free return label eligibility, and refund methods for AI shopping agents. Use when an AI shopping agent needs structured retailer return rules, including return window days, free return shipping eligibility, restocking fees, and refund methods by merchant domain. Do not use for product stock checks (use checkProductInventory) or general webpage scraping (use scrapeUrlToMarkdown).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "merchant_domain": "<merchant_domain>"
    },
    "name": "getMerchantReturnPolicy"
  }
}

Input Schema

Name	Required	Description	Default
`merchant_domain`	Yes	Retailer root domain name without http/https protocol (e.g., asos.com, bestbuy.com).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / merchant_domain / examples
```
Added value: +[
+  "bestbuy.com"
+]
```
- addedInput schema / properties / merchant_domain / pattern
```
Added value: +"^[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$"
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / merchant_domain / description

Previous value: -"Retailer domain name (e.g., asos.com, bestbuy.com, gymshark.com)"New value: +"Retailer root domain name without http/https protocol (e.g., asos.com, bestbuy.com)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It conveys that the tool parses retailer policies into structured fields, which implies a read-only lookup, but it says nothing about data freshness, source of the policy data, coverage gaps for merchants without a published policy, or failure behavior for unknown domains.

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?

Purpose is front-loaded and the exclusion sentence is compact. Minor redundancy: 'free return label eligibility' and 'free return shipping eligibility' restate the same field under two names, which slightly inflates the first sentence.

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?

With no output schema, the description usefully enumerates the field groups an agent can expect (window days, free return shipping, restocking fees, refund methods). What remains unstated is edge-case behavior for merchants lacking a published policy or unrecognized domains.

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 merchant_domain parameter is already documented with a pattern and example. The description reinforces that the key is a merchant domain, but adds no syntax or normalization guidance beyond the schema.

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?

A concrete verb plus resource, with the returned fields named (return windows, restocking fees, free return label eligibility, refund methods). It reads as unmistakably different from inventory, scraping, or pricing siblings.

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 'Use when' clause scoped to AI shopping agents needing structured retailer return rules, plus explicit exclusions that name the alternatives checkProductInventory and scrapeUrlToMarkdown. Routing is fully specified.

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

All mcp-livedatapro tools Inspect

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

Need Help?