Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_wallet_portfolio_composite

Fetch a wallet's USD portfolio across EVM chains or Solana, including native and major token balances, prices, and allocation.

Instructions

[On-Chain Intelligence] USD portfolio for an EVM or Solana wallet: native balance, major token balances, prices and allocation Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base|ethereum|arbitrum|optimism (EVM, default base). Solana is auto-detected from the address format
addressYesWallet address (0x... or Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/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 it does add real context: measured p50/p95 latency with a date and benchmark source, plus the upstream host. However, it omits auth/rate-limit expectations, error behavior for malformed addresses, and what counts as a 'major token' (token count, spam filtering), so the disclosure is partial for an unannotated tool.

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 core purpose is front-loaded in one compact sentence, followed by latency and endpoint details in a single trailing clause. Slightly boilerplate-ish benchmark and URL text keeps it from being maximally tight, but nothing is genuinely wasted.

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?

There is no output schema or annotations, so the description must describe returns itself, and enumerating native balance, token balances, prices, and allocation does that adequately for a two-parameter read tool. Remaining gaps are the definition of 'major tokens' and failure modes for invalid addresses.

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% and both parameters are already documented, including the chain enum values and Solana auto-detection. The description adds no syntax, format, or edge-case meaning beyond the schema, 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?

States a specific resource and scope: a USD-denominated portfolio for an EVM or Solana wallet, enumerating what is returned (native balance, major token balances, prices, allocation). This clearly separates it from single-token or price-only siblings, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

The description never says when to reach for this over siblings like caelara_crypto_token_price_aggregator or caelara_crypto_base_erc20_inspector, nor does it state any preconditions or exclusions. The only usage-adjacent hint is the chain default/Solana auto-detection, which is really parameter syntax rather than routing guidance.

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