Teardrop

Get Wallet Positions

get_wallet_positions

Read-only

Get a wallet's DeFi positions across all DeBank-supported chains and protocols. Returns protocol-level positions, asset/debt/net USD values, optional token lists, aggregate exposure, and optional all-chain net worth. Set include_token_balances=true to also return DeBank's complete cross-chain wallet token list. Set include_token_lists=false for a compact balance and debt summary without nested position tokens. This covers substantially more protocols and chains than the block-accurate get_defi_positions tool. Use raw-RPC tools for liquidation, swap quotes, or other transaction-critical questions.

Use when: Use for broad wallet discovery, portfolio allocation, protocol exposure, or cross-chain position questions. Set include_token_balances=true when complete wallet token discovery is required; otherwise the response only includes tokens attached to protocol positions. Set include_token_lists=false when only protocol balances, debt, or aggregate exposure are needed. Use get_defi_positions when the user needs a block-accurate Aave, Compound, Uniswap, or Lido snapshot.

Limitations: DeBank portfolio data is third-party analytics and may be stale, including occasional long refresh delays. It is read-only, EVM wallet oriented, and does not prove current liquidation or execution state. include_token_balances adds a separate billable DeBank request; include_token_lists only changes response detail.

Alternatives: get_defi_positions, get_wallet_portfolio, get_token_approvals

Input Schema

TableJSON Schema

Name	Required	Description
`wallet_address`	Yes	EVM wallet address (0x…)
`include_net_worth`	No	Include all-chain net worth and per-chain balances; disable to avoid that additional provider request.
`include_token_lists`	No	Include protocol position token lists; disable for a compact balance and debt summary.
`include_token_balances`	No	Include DeBank's complete cross-chain token balance list; adds a billable provider request.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No		Positions are sourced from DeBank Cloud portfolio analytics and may be stale; they are not block-accurate. staleness_seconds reports the oldest underlying position update. Use get_defi_positions or other raw-RPC tools for liquidation, quote, and transaction-critical checks.
`errors`	No
`positions`	No
`provenance`	Yes
`data_complete`	Yes
`total_net_usd`	No
`chain_balances`	No
`token_balances`	No
`total_debt_usd`	No
`wallet_address`	Yes
`total_asset_usd`	No
`include_net_worth`	Yes
`staleness_seconds`	No	Max age in seconds of the underlying DeBank position data (from per-item update_at), or None when unavailable.
`include_token_lists`	Yes
`total_net_worth_usd`	No
`include_token_balances`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 9, 2026

addedInput schema / properties / include_token_lists

Added value: +{
+  "default": true,
+  "description": "Include protocol position token lists; disable for a compact balance and debt summary.",
+  "title": "Include Token Lists",
+  "type": "boolean"
+}

addedOutput schema / properties / include_token_lists

Added value: +{
+  "title": "Include Token Lists",
+  "type": "boolean"
+}

addedOutput schema / properties / total_asset_usd

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Total Asset Usd"
+}

addedOutput schema / properties / total_debt_usd

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Total Debt Usd"
+}

addedOutput schema / properties / total_net_usd

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Total Net Usd"
+}

changedOutput schema / required

Previous value: -[
-  "wallet_address",
-  "include_net_worth",
-  "include_token_balances",
-  "data_complete",
-  "provenance"
-]New value: +[
+  "wallet_address",
+  "include_net_worth",
+  "include_token_balances",
+  "include_token_lists",
+  "data_complete",
+  "provenance"
+]

AddedAug 17, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing that data is third-party analytics, may be stale, may have long refresh delays, is EVM-wallet oriented, and does not prove current liquidation or execution state. It also transparently notes that include_token_balances triggers a separate billable provider request. There is no contradiction with the readOnlyHint annotation.

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?

The description is longer than average, but it is highly structured with clear sections: core capability, use cases, limitations, and alternatives. Every section earns its place, and the most important scoping differentiators are front-loaded. No redundant or filler sentences appear.

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?

Given the tool's complexity, four parameters, many sibling tools, and an existing output schema, the description is complete. It covers what the tool returns, when to use it, when to avoid it, parameter consequences, limitations, and alternatives. Nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Though the schema descriptions cover all four parameters, the tool description adds meaningful behavioral semantics: include_token_balances=true returns DeBank's complete cross-chain token list, while include_token_lists=false gives a compact balance/debt summary without nested tokens. It also clarifies that token lists only change response detail while token balances adds a billable request, which an agent needs to make informed decisions.

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 names a specific verb ('Get') and resource ('a wallet's DeFi positions across all DeBank-supported chains and protocols'), and specifies what is returned: protocol-level positions, asset/debt/net USD values, token lists, aggregate exposure, and all-chain net worth. It also explicitly differentiates from the sibling get_defi_positions by noting this tool covers substantially more protocols and chains.

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?

It has a dedicated 'Use when' section listing concrete use cases: broad wallet discovery, portfolio allocation, protocol exposure, and cross-chain position questions. It also explains when to toggle include_token_balances and include_token_lists, and explicitly directs users to get_defi_positions for block-accurate Aave/Compound/Uniswap/Lido snapshots. This is exemplary guidance.

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?