Skip to main content
Glama
Sign In
@blackwood-state/mcp

@blackwood-state/mcp

by Blackwood-State
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Wallet value in USD

blackwood_wallet_value

Retrieve a 0x wallet's USD net worth and token balances on Ethereum and Base in one call. Returns JSON with priced native and major tokens, per-chain totals, and unpriced tokens.

Instructions

Use when you need a wallet portfolio value in USD, a wallet net worth or token balances with USD value for a 0x address. Do not use for solana wallets, transaction history, NFTs, DeFi positions or long-tail tokens. Returns JSON with a wallet's USD value on Ethereum and Base in one call: native and major-token balances priced on-chain from Uniswap v3 pools on Base, per-chain totals and the tokens left unpriced for 0.005 USDC per call. Typical response time 5000 ms (p95). Category: Trading. Price: US$0.005 per call. A small free demo credit covers the first calls; after that the tool returns the command that pays the call from your own wallet (AgentCash or Coinbase Agentic Wallet).

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

Input Schema

NameRequiredDescriptionDefault
chainsNoChains to value (ethereum and base when omitted), e.g. ["base"]
addressYesWallet address (0x...) on Ethereum and Base, e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the pricing model (0.005 USDC per call, free demo credit, then an x402 payment command returned to the caller), latency (5000 ms p95), data provenance (Uniswap v3 pools on Base), and that unpriced long-tail tokens are surfaced rather than silently dropped. These operational traits are exactly what an agent needs before committing to a paid call.

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 sentence and the exclusion list before moving into return shape, latency, and pricing. Most sentences earn their place, though the category/price/demo-credit footer is somewhat verbose boilerplate.

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 and only two params, the description carries adequate weight: it describes the returned JSON (native and major-token balances, per-chain totals, unpriced tokens), states coverage limits, cost, and latency. The one real deficiency is the missing comparison against the near-identical wallet_balances and wallet_portfolio siblings.

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 (address and the chains enum array) are already fully documented in the schema, including the default of both chains when omitted. The description only restates the Ethereum/Base scope and adds no new syntax or constraint detail, 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 states a specific verb and resource: retrieve a wallet's USD portfolio value/net worth with priced token balances for a 0x address, on Ethereum and Base. It is clear what the tool does, but it never distinguishes itself from the very similar siblings blackwood_wallet_balances and blackwood_wallet_portfolio, so an agent still has to guess which of the three to pick.

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?

It gives explicit triggering conditions ("Use when you need a wallet portfolio value in USD... or token balances with USD value for a 0x address") and explicit exclusions (no Solana, transaction history, NFTs, DeFi positions, long-tail tokens). That is strong when/when-not guidance, but it never names an alternative tool to use instead for the excluded cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools