Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Wallet Holdings

octav_get_wallet
Read-only

Retrieve token balances and values across supported chains for a single wallet address, excluding DeFi protocol holdings. Use it to check wallet-only holdings without DeFi positions.

Instructions

Get wallet holdings only (excludes DeFi protocols). Returns token balances and values across all chains. Costs 1 credit per address.

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": {
      "addresses": "<addresses>"
    },
    "name": "octav_get_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesArray with one wallet address (EVM: 0x... or Solana base58). The API accepts one address per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / addresses / description
      Previous value: -"Array of wallet addresses (EVM: 0x... or Solana base58). Max 10 addresses."New value: +"Array with one wallet address (EVM: 0x... or Solana base58). The API accepts one address per call."
    • changedInput schema / properties / addresses / maxItems
      Previous value: -10New value: +1
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-annotation context: the cost of 1 credit per address and the DeFi exclusion. It does not describe pagination, failure modes for malformed addresses, or what a partial-chain failure looks like.

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 short sentences: what it returns, what it excludes, and what it costs. The scope constraint is front-loaded and nothing is redundant.

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?

For a single-parameter read tool with full schema coverage and annotations carrying the safety profile, the description covers scope, cost, and return contents. With no output schema, a brief note on the shape of the returned balance/value entries would close the remaining gap.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter already documents the EVM/Solana address formats and the one-address-per-call limit, so the baseline is 3. The description's 'costs 1 credit per address' adds billing meaning the schema lacks, and the addresses parameter must be an array of exactly one, consistent with that framing.

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 gives a specific verb and resource ('Get wallet holdings') and states scope precisely: token balances and values across all chains, excluding DeFi protocols. It implicitly separates the tool from portfolio-style siblings through the 'excludes DeFi' qualifier, though it never names the alternative that covers DeFi.

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

Usage Guidelines3/5

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

The parenthetical 'excludes DeFi protocols' implies when to reach for this tool versus a portfolio tool, but it never states the alternative or an explicit condition. An agent has to infer the routing rule rather than being told it.

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