Skip to main content
Glama

Agoranome buyer checks and market data

Wallet statement

spend_audit
Read-only

Use when a buyer agent or its operator must account for an x402 wallet's spending: a statement for a buyer wallet on Base. Every USDC payment checked against the payee's listed Bazaar price (above listed, oversize 10x or more, unlisted), spend and calls per seller, duplicate payments within a minute, payments after a seller's listing vanished or its pay-to changed, sellers whose certification failed since, whether the wallet looks sweep-like, and a CSV of every payment. 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": {
      "wallet": "<wallet>"
    },
    "name": "spend_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to look back
ticketNoOptional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.
walletYesBuyer wallet address on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / ticket
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.",
      +  "title": "Ticket"
      +}
  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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds the important commercial fact that the call is free ("no payment is asked"), plus the breadth of what the statement surfaces including a CSV of every payment. It does not discuss rate limits, failure modes, or the free-vs-ticket tradeoff (the schema covers ticket), but for a read-only audit it discloses enough beyond the annotations.

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?

It is front-loaded with the "Use when..." trigger and packs the check list into one dense parenthetical sequence with no filler sentences. The long run-on clause makes it slightly harder to scan, but every phrase carries information.

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?

With no output schema, the description compensates by naming the categories of findings and the CSV deliverable, and it states the cost model (free). Combined with readOnly/openWorld annotations and fully documented parameters, an agent has what it needs to invoke and interpret this correctly, though nothing is said about result size or error conditions.

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 description coverage is 100%: wallet, days (1-30, default 7) and ticket each carry their own schema text, including the full explanation of the ticket flow. The description adds no parameter-level meaning on top of that, 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 names a concrete verb and resource plus scope: a spending statement for a buyer wallet on Base, and enumerates the specific checks it performs (price variance vs Bazaar listing, per-seller spend, duplicate payments, delisted payees, failed certification, sweep-like patterns, CSV). That is far more than a restatement of the name. It stops short of naming a sibling it is distinguished from, so an agent must infer how it differs from e.g. payer_analytics.

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?

"Use when a buyer agent or its operator must account for an x402 wallet's spending" gives a clear triggering condition and audience. There are no explicit exclusions or named alternatives for the adjacent analytics tools, so the agent gets context but not routing rules.

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.