Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Net Asset Value

octav_get_nav
Read-only

Calculates total net worth (NAV) for up to 50 EVM or Solana wallet addresses in a selected currency such as USD, EUR, ETH, or SOL.

Instructions

Get total net worth (NAV) in specified currency. Supports USD, EUR, CAD, AED, CHF, SGD, ETH, SOL, cbBTC, EURC, BNB, WHYPE. 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_nav"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency for NAV calculation. Defaults to USD.USD
addressesYesArray of wallet addresses (EVM: 0x... or Solana base58). Max 50 addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 of wallet addresses (EVM: 0x... or Solana base58). Max 50 addresses."
    • changedInput schema / properties / addresses / maxItems
      Previous value: -10New value: +50
    • changedInput schema / properties / currency / enum
      Previous value: -[
      -  "USD",
      -  "EUR",
      -  "GBP",
      -  "JPY",
      -  "CNY"
      -]New value: +[
      +  "USD",
      +  "EUR",
      +  "CAD",
      +  "AED",
      +  "CHF",
      +  "SGD",
      +  "ETH",
      +  "SOL",
      +  "cbBTC",
      +  "EURC",
      +  "BNB",
      +  "WHYPE"
      +]
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-destructive, open-world operation. The description adds a meaningful behavioral fact beyond the annotations: it costs 1 credit per address and lists supported currencies. It does not explain aggregation behavior for multiple addresses or any rate-limit details beyond credits.

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 two tight sentences with the core purpose and cost front-loaded. Every sentence adds information: what is returned, which currencies are supported, and the credit cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and the input schema is fully documented, but there is no output schema and the description does not clarify whether multiple addresses produce a single aggregate NAV or per-address values. For a multi-address NAV call, that return-shape ambiguity is a meaningful gap.

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 currency enum, address format, required status, and 50-address limit are already documented in the schema. The description restates supported currencies and notes per-address credit cost, adding only marginal meaning beyond the structured parameter data.

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 states a specific verb and resource: get total net worth (NAV) in a specified currency. That is clearer than a generic portfolio call, but it does not explicitly distinguish this tool from siblings such as octav_get_portfolio or octav_get_historical.

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 when the tool is useful: when the agent needs total NAV across one or more addresses. It gives no explicit exclusions or comparison to alternatives, so the agent must infer the choice from the tool name and output concept.

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