Skip to main content
Glama

Merchant Domain Scam & Rug-Pull Guard MCP

Extract Refund Policy Summary ($0.005 USDC)

extract_refund_policy_summary
Read-onlyIdempotent

Call this tool BEFORE purchasing physical goods or high-value items to discover and parse a merchant's refund/return policy page into structured terms (return window, restocking fees, contact email, scam template red flags). Cost: $0.005 USDC (Base via x402 PayAI).

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": {
      "domain_or_url": "<domain_or_url>"
    },
    "name": "extract_refund_policy_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_or_urlYesMerchant domain or direct URL to the merchant's refund/returns policy page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The description adds genuinely new context: the tool is paid, at $0.005 USDC via Base/x402 PayAI, which an agent must know before invoking and which no structured field conveys. It leaves out error behavior (e.g., what happens if no policy page is found) and whether content is cached.

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?

One dense sentence with no filler, and the actionable trigger ('Call this tool BEFORE purchasing...') is front-loaded. The cost and payment rail are appended at the tail where they are slightly easier to miss than a leading imperative would be.

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?

For a one-parameter read tool with rich annotations and no output schema, the description covers the trigger condition, the extracted fields, and the payment cost. Missing only failure-mode guidance and any statement about whether the URL must be publicly reachable.

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?

There is a single parameter at 100% schema description coverage; the schema already explains it accepts a merchant domain or a direct policy URL. The description reinforces 'merchant's refund/return policy page' but adds no format examples or fallback behavior beyond that. Baseline 3 applies when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (parse/extract) and resource (merchant refund/return policy page) and enumerates the extracted fields (return window, restocking fees, contact email, scam red flags), so the agent knows exactly what comes back. It doesn't explicitly contrast with the sibling verify_merchant_trust, which also touches on merchant trust signals, so sibling differentiation is only implied by the 'policy page' scope.

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?

'Call this tool BEFORE purchasing physical goods or high-value items' gives a clear triggering condition tied to transaction value. It stops short of naming when NOT to use it or pointing to the sibling alternatives (inspect_checkout_url, verify_merchant_trust).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.