Skip to main content
Glama

Arc wallet history

arc_wallet_history

Wallet history on Arc: the last 50 transfers in and out of an address over about 3 days, decoded (time, direction, from, to, token, amount, USD at the time of the transfer and today) plus net flow per token (accumulating or distributing). USDC counted once from native transfer logs; NFTs listed; impostor USDC/EURC and address poisoning (lookalike addresses, events the sender never signed) flagged. A failed read is refused before payment. $0.003 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": {
      "address": "<address>"
    },
    "name": "arc_wallet_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNooptional: a block number; returns the page ending at it (each answer gives next.before)
addressYesArc address (0x...)
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. Changed1 schema field changed
    • addedInput schema / properties / before
      Added value: +{
      +  "description": "optional: a block number; returns the page ending at it (each answer gives next.before)",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses the 3-day/50-transfer window, pagination via with next.before, USDC de-duplication from native logs, impostor token and address-poisoning flagging, and the two-step x402 payment flow with cost of $0.003 per call. It also states a failed read is refused before payment, which is real behavioral value. Remaining gaps are rate limits, behavior for invalid addresses, and term expiry between the two calls.

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 paragraph is front-loaded with the resource and window, then flags, then payment and invocation, so the important facts come early. It is dense and semicolon-heavy but nearly every clause carries information. Minor cost from running the cost and payment sequence together into the same block as data-description content.

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 tool with no annotations and no output schema, the definition covers return fields, de-duplication, flags, pagination hints and payment mechanics, which is close to what an agent needs. The main unresolved point is that a '~3 days / last 50' window coexists with a before-cursor that implies deeper paging, leaving the true historical depth ambiguous.

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 the baseline is 3 and the schema already documents address, before and payment. The description adds the useful clarification that the first call without payment returns terms to be signed before the second call completes the purchase, which supplements the schema's payment text. It adds nothing beyond the schema for before or address, and the stated ~3-day window sits somewhat awkwardly with a block-number pagination cursor.

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 and pins down scope precisely: the last 50 transfers in and out of an address over roughly 3 days, decoded into time, direction, from, to, token, amount and USD values. It also states the analytical add-ons (net flow per token, NFT listing, impostor and poisoning flags). It never names the closely related siblings arc_wallet or arc_wallet_value, so the agent must infer the boundary from content alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope statement (recent transfers plus net flow, not balances or valuation) implies when the tool is appropriate, and the payment instructions describe a concrete invocation sequence. However, there is no explicit when-to-use/when-not-to-use statement and no alternatives are named, which matters given siblings like arc_wallet, arc_wallet_value and arc_counterparty that overlap in domain.

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