Skip to main content
Glama

Agoranome buyer checks and market data

Buyer check

buyer_check
Read-only

Use when a buyer agent is about to pay an x402 seller it hasn't paid before, or above its usual amount: a signed verdict from what Agoranome holds: the Fair Offer block and certification, the pay-to and since when, OFAC sanctions on it, Google Web Risk on the URL, price against listing and quote, verified deliveries, policy tiers met. Give url= up to 20 times to rank sellers safest first. With tx=, settlement proof: the USDC transfer on Base, Monad or Solana and if it matched the quote. Free: no payment is asked.

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": {
      "url": "<url>"
    },
    "name": "buyer_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
txNoSettlement mode: the payment's transaction hash on Base or Monad, or its signature on Solana
urlYesThe x402 offer's URL, or a list of up to 20 offer URLs to check in one call for the same price, listed safest first
shareNoSettlement mode: publish the buyer-side receipt in the evidence commons
pay_toNoThe quoted pay-to address
networkNoSettlement mode: eip155:8453 (Base, the default), eip155:143 (Monad) or solana
max_priceNoYour per-call cap in USD
accept_proofNoYour requirements, as an Accept-Proof value
expected_priceNoThe quoted price in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / network
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "eip155:8453",
      +        "eip155:143",
      +        "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
      +        "solana"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Settlement mode: eip155:8453 (Base, the default), eip155:143 (Monad) or solana",
      +  "title": "Network"
      +}
    • changedInput schema / properties / pay_to / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^0x[0-9a-fA-F]{40}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^(0x[0-9a-fA-F]{40}|[1-9A-HJ-NP-Za-km-z]{32,44})$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / tx / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^0x[0-9a-fA-F]{64}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^(0x[0-9a-fA-F]{64}|[1-9A-HJ-NP-Za-km-z]{64,90})$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / tx / description
      Previous value: -"Settlement mode: the payment's transaction hash on Base"New value: +"Settlement mode: the payment's transaction hash on Base or Monad, or its signature on Solana"
  2. Changed1 schema field changed
    • removedInput schema / properties / kyapay-token
      Removed value: -{
      -  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / kyapay-token
      Added value: +{
      +  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
      +  "type": "string"
      +}
  4. Changed5 schema fields changed
    • addedInput schema / properties / url / anyOf
      Added value: +[
      +  {
      +    "maxLength": 2048,
      +    "minLength": 10,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "maxLength": 2048,
      +      "minLength": 10,
      +      "type": "string"
      +    },
      +    "maxItems": 20,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / url / description
      Previous value: -"The x402 offer's URL"New value: +"The x402 offer's URL, or a list of up to 20 offer URLs to check in one call for the same price, listed safest first"
    • removedInput schema / properties / url / maxLength
      Removed value: -2048
    • removedInput schema / properties / url / minLength
      Removed value: -10
    • removedInput schema / properties / url / type
      Removed value: -"string"
  5. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark it read-only and open-world, so the lower bar applies, and the description still adds real context: the result is 'signed,' the checks include external signals (OFAC, Web Risk), a tx= call switches into settlement-proof mode covering the actual USDC transfer and quote match, and 'Free: no payment is asked' clarifies there is no cost. It does not spell out failure modes or what a negative verdict looks like.

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?

The triggering condition is front-loaded and the content is dense with specifics rather than filler. The colon-chained list and unexplained brand reference ('what Agoranome holds') make it slightly harder to parse than it needs to be.

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?

With eight parameters, no output schema, and only mild annotations, the description should carry more weight. It describes the verdict's ingredients in prose but not the shape of the returned verdict, and it documents only the url and tx parameters, leaving the remaining six entirely to the schema.

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 100%, so the baseline is 3; the description adds mode-level meaning beyond the schema by explaining that repeated url values rank sellers safest first and that supplying tx= switches the call into settlement-proof mode. It leaves the non-mode parameters (share, accept_proof, max_price, expected_price) to the schema, so it is not fully additive.

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 states a concrete verb and resource: it returns a signed verdict on an x402 seller before payment, and it enumerates what the verdict covers (Fair Offer block, certification, pay-to history, OFAC sanctions, Web Risk, price vs. listing/quote, verified deliveries, policy tiers). The purpose is unmistakable, but it never contrasts itself with close siblings such as check_fair_offer or check_offer, so an agent must still infer which check to run.

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?

Timing guidance is explicit and actionable: use it when 'a buyer agent is about to pay an x402 seller it hasn't paid before, or above its usual amount.' That gives a clear triggering condition. It stops short of naming alternatives or when-not-to-use cases, which keeps it below a 5.

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.