Teardrop

Get Wallet Portfolio

get_wallet_portfolio

Read-only

Get aggregated token holdings with USD values for a wallet address. Tracks 19 major assets on Ethereum and 12 on Base, including spot, lending, liquid-staking, restaking, and stablecoin assets. Sorted by USD value. Returns up to 20 holdings. Includes native ETH balance in the holdings list — calling get_eth_balance separately after this is redundant.

Use when: Choose when you need a wallet's overall token exposure and USD value on Ethereum or Base in one call. Call once per chain for a cross-chain comparison.

Limitations: Tracks a fixed set of major assets per chain, not arbitrary tokens. Returns up to 20 holdings. Native ETH is included, so calling get_eth_balance separately is redundant.

Alternatives: get_eth_balance, get_token_price, get_defi_positions

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain_id`	No	Chain ID (1=Ethereum, 8453=Base)
`wallet_address`	Yes	Wallet address (0x…)

Output Schema

TableJSON Schema

Name	Required	Default
`note`	No	Only tracked tokens shown. Untracked tokens not included.
`chain_id`	Yes
`holdings`	Yes
`fetch_errors`	No
`wallet_address`	Yes
`total_value_usd`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```
addedInput schema / properties / wallet_address / title
```
Added value: +"Wallet Address"
```

addedInput schema / title

Added value: +"mcp_get_wallet_portfolioArguments"

addedOutput schema / $defs

Added value: +{
+  "PortfolioEntry": {
+    "properties": {
+      "balance_formatted": {
+        "title": "Balance Formatted",
+        "type": "string"
+      },
+      "price_usd": {
+        "title": "Price Usd",
+        "type": "number"
+      },
+      "symbol": {
+        "title": "Symbol",
+        "type": "string"
+      },
+      "token_address": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "title": "Token Address"
+      },
+      "value_usd": {
+        "title": "Value Usd",
+        "type": "number"
+      }
+    },
+    "required": [
+      "symbol",
+      "token_address",
+      "balance_formatted",
+      "price_usd",
+      "value_usd"
+    ],
+    "title": "PortfolioEntry",
+    "type": "object"
+  }
+}

addedOutput schema / properties / holdings / items / $ref
```
Added value: +"#/$defs/PortfolioEntry"
```

removedOutput schema / properties / holdings / items / properties

Removed value: -{
-  "balance_formatted": {
-    "title": "Balance Formatted",
-    "type": "string"
-  },
-  "price_usd": {
-    "title": "Price Usd",
-    "type": "number"
-  },
-  "symbol": {
-    "title": "Symbol",
-    "type": "string"
-  },
-  "token_address": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "title": "Token Address"
-  },
-  "value_usd": {
-    "title": "Value Usd",
-    "type": "number"
-  }
-}

removedOutput schema / properties / holdings / items / required

Removed value: -[
-  "symbol",
-  "token_address",
-  "balance_formatted",
-  "price_usd",
-  "value_usd"
-]

removedOutput schema / properties / holdings / items / title
```
Removed value: -"PortfolioEntry"
```
removedOutput schema / properties / holdings / items / type
```
Removed value: -"object"
```

First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden of behavioral disclosure. It adds useful detail beyond the schema: results are sorted by USD value, limited to 20 holdings, include native ETH, and are restricted to a fixed asset set. This goes beyond what annotations provide, though it could still be more explicit about response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized into useful sections (Use when, Limitations, Alternatives) and front-loads the core action, but it contains redundancy: the native ETH redundancy warning and the 20-holding limit are each stated twice. Tightening those repetitions would make it more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only portfolio tool with a full input schema and output schema, this description is complete. It covers when to use it, how to use it across chains, what it does and does not capture, and how it relates to sibling tools, leaving no critical gap for an agent.

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 the schema already documents both parameters. The description adds contextual color about Ethereum/Base and native ETH inclusion, but does not fundamentally expand on the schema's parameter meanings. A score of 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Get aggregated token holdings with USD values for a wallet address.' It also adds concrete scope details (chains, asset types, sorting, cap of 20) that clearly distinguish this tool from siblings like get_eth_balance and get_defi_positions.

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

Usage Guidelines5/5

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

The description includes an explicit 'Use when' section, states the per-chain calling pattern for cross-chain comparisons, and lists alternatives. It also communicates when the tool is insufficient via limitations like 'Tracks a fixed set of major assets per chain, not arbitrary tokens.'

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

All Teardrop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?