Skip to main content
Glama

zato crypto data

Wallet age: when did this address first become active (Ethereum, Base, Optimism)

wallet_age
Read-only

When did this address first become active (first outgoing tx / contract creation) on Ethereum, Base and Optimism. Price: $0.002 USDC per call (x402, Base).

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": "wallet_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNooptional subset: ethereum,base,optimism (default all three)
addressYeswallet/contract address or ENS/Basename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context beyond that, and it does: it discloses paid access ($0.002 USDC via x402 on Base) and precisely defines the activity boundary (first outgoing tx or contract creation). It doesn't mention rate limits, failure modes, or how inactive/nonexistent addresses are handled.

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?

Two short sentences, front-loaded with the core question and metric definition, followed by pricing. Every clause carries information an agent needs; nothing is filler.

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?

Covers purpose, metric definition, chain scope, and cost, which is enough to call it correctly despite having no output schema. A brief note on the expected return shape (e.g., per-chain timestamps) or on addresses with no activity would close the remaining 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 description coverage is 100%, so both parameters are already documented, including the chain subset and default. The description only restates the chain list, adding no format or edge-case detail (e.g., case handling, ENS resolution behavior) beyond the schema.

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?

States a specific question ('when did this address first become active') and pins down the metric definition (first outgoing tx / contract creation) plus the chains covered. It is clearly narrower than siblings like wallet_report or batch_wallet_report, though it doesn't explicitly name a sibling to contrast with.

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?

Usage is implied by the narrow single-metric scope and reinforced by the stated per-call price, which helps an agent judge whether the call is worth it. However, there is no explicit when-not guidance or pointer to alternative tools such as a full wallet report when more than age is needed.

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