Skip to main content
Glama

Ellimist

Account snapshot

data_chain_account
Read-only

Use this to know everything basic about a wallet in one call: native and USDC balances (plus up to 5 tokens you name), nonce, whether it is a contract or an EIP-7702 delegated account, whether its public key is already revealed on this chain (quantum exposure), contract details (code size, minimal proxy, owner) and an official OFAC sanctions check. All read at once. Price: $0.01 USDC per call via x402 (no account). Not charged if it fails.

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

Input Schema

NameRequiredDescriptionDefault
chainNoethereum
tokensNoextra ERC-20 tokens to include (native USDC is always included)
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 added value is the commercial and failure behavior: $0.01 USDC per call via x402, no account required, and not charged if it fails. Disclosing the cost model and the no-charge-on-failure guarantee is genuinely decision-relevant for an agent. It does not describe the response shape or timing, which keeps it off a 5.

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 the use case, then a dense but purposeful enumeration, then a short pricing sentence. Nothing is filler — even the price sentence earns its place because it changes whether an agent should call this. The returning-fields clause is long and comma-chained, which costs a point on readability but not on 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?

With no output schema, the description carries the return-value burden and does so by listing every returned facet, which is the right call for a bundled snapshot tool. Cost and failure charging are covered. What is missing is the response container/format and any note on whether sanctions results are boolean or detailed — minor for a 3-parameter read tool.

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 only 33%, so the description has to compensate, and it partially does: 'up to 5 tokens you name' clarifies the tokens array (mirroring the maxItems cap, with native USDC always included), and 'on this chain' ties to the chain enum. The address parameter gets no treatment at all, and there is no guidance on chain selection beyond the default, leaving a real gap.

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 specific verb-and-resource bundle ('know everything basic about a wallet in one call') and then enumerates the exact fields returned: balances, nonce, contract/EIP-7702 status, key-reveal exposure, contract details, and an OFAC check. That is far more concrete than a title restatement. It stops short of naming which sibling to prefer when only one of those facets is needed, so it lands at 4 rather than 5.

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?

'Use this to know everything basic about a wallet in one call' implies the use case (bulk snapshot instead of several calls), and naming an x402 price signals this is a paid call worth batching. But there is no explicit when-not guidance and no named alternative such as data_risk_ofac for a sanctions-only query or data_chain_erc20_transfers for transfer history. Usage is implied, not directed.

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