Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Full Portfolio

octav_get_portfolio
Read-only

Fetch a wallet's complete portfolio across 20+ blockchains, returning token balances, values, and DeFi protocol positions; optionally wait for a fresh sync.

Instructions

Get complete portfolio including wallet holdings and DeFi protocol positions across 20+ blockchains. Returns token balances, values, and protocol positions. Waits for a fresh sync by default. 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_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesArray with one wallet address (EVM: 0x... or Solana base58). The API accepts one address per call.
waitForSyncNoWait for a fresh sync when cached data is stale (default: true). Set false to return cached data immediately.
includeExplorerUrlsNoInclude blockchain explorer URLs for assets and transactions (default: false)

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. Changed2 schema fields changedv1.2.1
    • addedInput schema / properties / includeExplorerUrls
      Added value: +{
      +  "default": false,
      +  "description": "Include blockchain explorer URLs for assets and transactions (default: false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / waitForSync
      Added value: +{
      +  "default": true,
      +  "description": "Wait for a fresh sync when cached data is stale (default: true). Set false to return cached data immediately.",
      +  "type": "boolean"
      +}
  3. First observedv1.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses two genuinely useful operational facts: a credit cost of 1 per address and that the call blocks waiting for a fresh sync by default. It stops short of describing response shape or how partial chain failures are handled, which matters for an open-world aggregation 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?

Four short sentences, front-loaded with the scope before cost and latency details; nothing is buried. Slight redundancy between 'complete portfolio including wallet holdings and DeFi protocol positions' and 'Returns token balances, values, and protocol positions' costs it a point.

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?

With no output schema, the description must characterize the return payload, and it does so at a high level (balances, values, protocol positions across chains). Combined with the credit cost and sync-latency disclosure, an agent has enough to decide and invoke correctly, though the response envelope remains unspecified.

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 all three parameters are already documented, including the single-address constraint and the waitForSync default. The description adds only the framing that credits are charged per address, which lightly reinforces the maxItems=1 restriction but adds no new format or syntax detail.

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 verb and resource (get complete portfolio) plus the scope of what is included: wallet holdings, DeFi protocol positions, and 20+ blockchains. It does not name or contrast with the closely related siblings octav_get_portfolio_at_block or octav_get_virtual_users_portfolio, so the agent must infer the distinction from the tool name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives in the sibling list (point-in-time portfolio, virtual-users portfolio, per-chain endpoints). The only quasi-guidance is the sync behavior statement, which duplicates the schema default rather than helping the agent choose between tools.

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