Skip to main content
Glama

Wrong pay

wrong_pay
Read-onlyIdempotent

Check an Arc USDC payment transaction hash for address poisoning lookalikes or OFAC SDN exposure. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "tx": "<tx>"
    },
    "name": "wrong_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNooptional recipient to evaluate when multiple transfers exist
txYesArc transaction hash (0x + 64 hex)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, open-world), so the description adds genuinely new context: the $0.005 price, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the wallet-signing requirement. It does not explain what happens if payment is invalid or whether unpaid calls are rate-limited, but the core behavioral picture is solid.

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?

Three sentences, front-loaded with what is checked, followed by cost and the payment handshake. Every sentence carries information the agent needs, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The payment flow is well covered, but there is no output schema and the description never indicates what a result looks like — flags, match/no-match, risk score, or error states for an unknown hash. For a verdict-returning screening tool, that leaves a meaningful gap.

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 each parameter is already documented, including the payment payload semantics. The description reinforces the payment handshake but adds no format or constraint detail beyond what the schema states, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ('Check an Arc USDC payment transaction hash') and names the two things it evaluates: address-poisoning lookalikes and OFAC SDN exposure. It does not explicitly distinguish itself from related siblings such as arc_impostors or arc_contract_check, so an agent still has to infer which check it needs.

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?

Clear procedural guidance is given: call once without `payment` to get terms, sign with your own wallet, then call again with `payment`. This tells the agent exactly how to sequence calls. It stops short of saying when to prefer this tool over sibling screening tools.

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