Skip to main content
Glama
Octav-Labs

Octav API MCP Server

Official
by Octav-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Full Portfolio

octav_get_portfolio
Read-only

Retrieve complete crypto portfolio data across 20+ blockchains, including wallet token holdings, values, and DeFi protocol positions. Returns balances for up to 10 EVM or Solana addresses.

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.

Input Schema

NameRequiredDescriptionDefault
addressesYesArray of wallet addresses (EVM: 0x... or Solana base58). Max 10 addresses.
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.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"
+}
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior. The description adds meaningful operational context beyond annotations: it waits for a fresh sync by default and costs 1 credit per address, which is important for invocation planning.

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?

Four short sentences, front-loaded with purpose and followed by return content, sync behavior, and cost. Every sentence carries useful information with no redundancy.

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?

No output schema is present, so the description usefully summarizes return content as token balances, values, and protocol positions. Combined with schema coverage and annotations, it is nearly complete, though it could mention latency or stale-cache implications more explicitly.

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 coverage is 100%, so the schema already documents addresses, waitForSync, and includeExplorerUrls. The description only restates the default sync behavior and per-address credit cost, without adding further parameter semantics; baseline 3 is appropriate.

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, including wallet holdings and DeFi protocol positions across 20+ blockchains. It is clearly more expansive than wallet or token-specific siblings, though it does not explicitly distinguish itself from close siblings like octav_agent_portfolio or octav_get_portfolio_at_block.

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 description implies this is the comprehensive portfolio tool and notes cost and sync behavior, but it does not say when to use it instead of octav_get_wallet, octav_get_token_overview, octav_agent_portfolio, or octav_get_portfolio_at_block. Usage is reasonably implied but not explicitly routed.

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

Deploy Server

Other Tools