Skip to main content
Glama

Genesis402 by UnyKorn (x402 pay-per-call)

Wallet risk brief

genesis402_wallet_brief

Paid ($0.03 USDC). Full risk brief for one EVM wallet in a single call: sanctions-list check (OFAC SDN digital-currency entries), native balance and activity scan across 10 EVM chains, recent activity on the chosen chain and a plain-language summary. Use before sending funds to, or accepting funds from, an unknown address. For a sanctions check alone use genesis402_screen_sanctions (cheaper, any chain); for balances without risk signals use genesis402_multi_chain_scan; for a token contract use genesis402_token_brief. Returns each part with its own sources (a part that cannot be read is marked unavailable with the reason, never zeroed) and an evidence hash over all parts. Heuristic signals from public data: not KYC, not a compliance determination, not legal advice. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoOptional EVM chain name to focus on, e.g. ethereum or base. Omit to cover all supported chains.
addressYesThe EVM wallet address to check, 0x followed by 40 hex characters. Checksum case is optional.
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesQUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
paidYestrue only when a payment was settled for this call.
priceNoThe Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
resultNoPAID or FREE: the endpoint's JSON result.
resourceNoQUOTE_ONLY: the full URL of the paid resource.
how_to_payNoQUOTE_ONLY: how to sign and resend the call.
settlementNoPAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
what_you_getNoQUOTE_ONLY: the rail's description of what the payment buys.
payment_required_b64NoQUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
also_accepted_networksNoQUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"EVM address, 0x followed by 40 hex characters."New value: +"The EVM wallet address to check, 0x followed by 40 hex characters. Checksum case is optional."
    • changedInput schema / properties / chain / description
      Previous value: -"Optional chain name, e.g. ethereum, base, polygon, arbitrum. Defaults to ethereum."New value: +"Optional EVM chain name to focus on, e.g. ethereum or base. Omit to cover all supported chains."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • changedOutput schema / properties / also_accepted_networks / description
      Previous value: -"Other payment networks this endpoint accepts."New value: +"QUOTE_ONLY: every network the 402 challenge accepts."
    • changedOutput schema / properties / how_to_pay / description
      Previous value: -"How to pay for this call."New value: +"QUOTE_ONLY: how to sign and resend the call."
    • changedOutput schema / properties / mode / description
      Previous value: -"QUOTE_ONLY when no payment was made; the quote is in price."New value: +"QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment."
    • addedOutput schema / properties / mode / enum
      Added value: +[
      +  "QUOTE_ONLY",
      +  "PAID",
      +  "FREE"
      +]
    • changedOutput schema / properties / paid / description
      Previous value: -"true or the paid quote when payment settled."New value: +"true only when a payment was settled for this call."
    • addedOutput schema / properties / paid / type
      Added value: +"boolean"
    • changedOutput schema / properties / payment_required_b64 / description
      Previous value: -"The raw x402 PAYMENT-REQUIRED header, base64."New value: +"QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client."
    • addedOutput schema / properties / price / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "atomic": {
      +        "description": "Price in USDC atomic units (6 decimals), as a decimal string.",
      +        "type": "string"
      +      },
      +      "network": {
      +        "description": "CAIP-2 network id of the lane, eip155:8453 (Base).",
      +        "type": "string"
      +      },
      +      "payTo": {
      +        "description": "Address the payment settles to.",
      +        "type": "string"
      +      },
      +      "usd": {
      +        "description": "Price in US dollars.",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "atomic",
      +      "usd",
      +      "payTo",
      +      "network"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / price / description
      Previous value: -"Quote on Base USDC: atomic, usd, payTo, network."New value: +"The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment."
    • changedOutput schema / properties / resource / description
      Previous value: -"The endpoint URL that was quoted or called."New value: +"QUOTE_ONLY: the full URL of the paid resource."
    • changedOutput schema / properties / result / description
      Previous value: -"The endpoint's response data."New value: +"PAID or FREE: the endpoint's JSON result."
    • changedOutput schema / properties / settlement / description
      Previous value: -"Decoded x402 settlement (tx hash, network, payer)."New value: +"PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none."
    • changedOutput schema / properties / what_you_get / description
      Previous value: -"What the paid call returns."New value: +"QUOTE_ONLY: the rail's description of what the payment buys."
    • addedOutput schema / properties / what_you_get / type
      Added value: +"string"
    • addedOutput schema / required
      Added value: +[
      +  "mode",
      +  "paid"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"EVM address, 0x followed by 40 hex characters."
    • addedInput schema / properties / chain / description
      Added value: +"Optional chain name, e.g. ethereum, base, polygon, arbitrum. Defaults to ethereum."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "also_accepted_networks": {
      +      "description": "Other payment networks this endpoint accepts.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "how_to_pay": {
      +      "description": "How to pay for this call.",
      +      "type": "string"
      +    },
      +    "mode": {
      +      "description": "QUOTE_ONLY when no payment was made; the quote is in price.",
      +      "type": "string"
      +    },
      +    "paid": {
      +      "description": "true or the paid quote when payment settled."
      +    },
      +    "payment_required_b64": {
      +      "description": "The raw x402 PAYMENT-REQUIRED header, base64.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "price": {
      +      "description": "Quote on Base USDC: atomic, usd, payTo, network."
      +    },
      +    "resource": {
      +      "description": "The endpoint URL that was quoted or called.",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "The endpoint's response data."
      +    },
      +    "settlement": {
      +      "description": "Decoded x402 settlement (tx hash, network, payer)."
      +    },
      +    "what_you_get": {
      +      "description": "What the paid call returns."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the paid nature ($0.03 USDC), the two-step quote-then-sign payment protocol, the failure semantics ('a part that cannot be read is marked unavailable with the reason, never zeroed'), the evidence hash output, and explicit non-goals (not KYC, not a compliance determination, not legal advice). The readOnlyHint=false annotation is consistent with the payment/settlement behavior described.

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?

Front-loaded with purpose and price; sentence order (what it is → when to use → alternatives → returns → disclaimers → payment) is logical. It is dense with several sentences, but essentially every one carries distinct information; only minor tightening is possible.

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

Completeness5/5

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

For a 3-parameter paid tool with an output schema, the description covers everything an agent needs: cost, payment handshake, scope of chains, per-part sourcing and unavailability behavior, disclaimers, and sibling routing. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: it explains chains scope ('recent activity on the chosen chain') and, crucially, the operational contract for payment_signature — omit it first to obtain an uncharged quote, resend with the signed payment. The address parameter itself adds nothing 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?

States a specific resource and scope ('Full risk brief for one EVM wallet in a single call') and enumerates the constituent parts: sanctions check, native balance/activity across 10 chains, recent chain activity, and a summary. It also names the sibling tools it is not, so an agent can distinguish it without opening any schema.

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?

Gives an explicit usage trigger ('Use before sending funds to, or accepting funds from, an unknown address') and routes to three named alternatives with the condition that selects each: screen_sanctions for sanctions alone, multi_chain_scan for balances without risk signals, token_brief for token contracts.

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.