Skip to main content
Glama

Merchant Domain Scam & Rug-Pull Guard MCP

Inspect Checkout URL ($0.005 USDC)

inspect_checkout_url
Read-onlyIdempotent

ALWAYS call this tool BEFORE navigating to a checkout URL or submitting card/wallet payment credentials to audit for redirect hijacking, domain mismatch, IDN spoofing, TLS validity, payment processor identity, and URLhaus malware listing. 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": {
      "checkout_url": "<checkout_url>"
    },
    "name": "inspect_checkout_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkout_urlYesFull HTTPS/HTTP checkout URL the agent is about to visit or submit payment to.
expected_merchant_domainNoOptional storefront domain where the item was found, to detect unexpected cross-domain checkout redirects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered structurally. The description does add genuinely non-redundant context: the concrete audit checklist and the $0.005 USDC charge via x402 PayAI on Base, which matters for an agent deciding whether to spend. However, it says nothing about what the tool returns (verdict, risk factors, pass/fail), which is the biggest behavioral unknown for a security gate.

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?

One front-loaded sentence: imperative trigger first, audit scope second, price last. The six-item checklist is dense but every item carries distinct decision value, and the cost clause is separated cleanly at the end. No filler wording.

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 two-parameter, read-only inspection tool the description covers trigger, scope, and pricing well, and the schema fully documents inputs. The notable omission is return-value behavior: with no output schema, the agent cannot tell whether it receives a boolean, a risk score, or a list of findings, which is significant for a tool meant to gate a payment decision.

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%, so both parameters are fully documented in the schema itself, establishing a baseline of 3. The description's mention of 'domain mismatch' loosely motivates expected_merchant_domain, but adds no format, syntax, or semantics beyond what the schema already explains.

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 and resource ('inspect/audit a checkout URL') and enumerates exactly what the audit covers: redirect hijacking, domain mismatch, IDN spoofing, TLS validity, processor identity, and URLhaus listing. The safety-audit angle clearly separates it from siblings like verify_merchant_trust (merchant reputation) and extract_refund_policy_summary (policy text).

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?

Gives an explicit, emphatic trigger: 'ALWAYS call this tool BEFORE navigating to a checkout URL or submitting card/wallet payment credentials.' That pins down the moment of invocation precisely. It stops short of naming sibling tools or stating when-not to use it, so it falls just below the top band.

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.

Resources