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.

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. Dates show when Glama detected each change.

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.5/5.0

Behavior5/5

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

Despite having readOnlyHint annotation, the description adds valuable context: it lists asset categories, chain coverage, sorting by USD value, a hard limit of 20 holdings, and the inclusion of native ETH. This goes well beyond the annotation to set expectations about the returned data.

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?

Three sentences, each providing distinct information: overall function, coverage/scope, and a usage caveat. No wasted words, and the most important detail is front-loaded.

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?

With an output schema present and read-only annotation, the description fully covers the tool's behavior, including limits, sorting, and coverage. It provides enough context for an agent to decide when to call it.

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?

Both parameters have detailed descriptions in the schema (wallet address, chain_id with chain IDs). The description reinforces the chain coverage but does not add new parameter-specific information, so schema carries the burden.

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 uses a specific verb ('Get aggregated token holdings with USD values') and clearly identifies the resource (wallet address). It also distinguishes from siblings by noting that native ETH balance is included, making a subsequent get_eth_balance call redundant.

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?

The description explicitly warns against calling get_eth_balance separately, which is a clear exclusion. It also implies this tool is for broad portfolio views across supported chains, though it doesn't enumerate all alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources

Need Help?