Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Token Distribution

octav_get_token_overview
Read-only

Retrieve an aggregated token distribution for a wallet on a specified date, including held tokens, values, and percentage breakdown across all chains.

Instructions

Get aggregated token distribution across all chains. Shows which tokens you hold, their values, and percentage breakdown. 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>",
      "date": "<date>"
    },
    "name": "octav_get_token_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate for token overview snapshot (YYYY-MM-DD format)
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.5/5.0
Behavior3/5

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

Annotations already cover read-only, open-world, and non-destructive behavior, so the description does not need to restate safety. It does add one genuinely new behavioral fact — a cost of 1 credit per address — but says nothing about pagination, whether unsupported chains are silently skipped, or how zero-balance tokens are treated.

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?

Three short sentences with the core purpose front-loaded and no filler. The breakdown enumeration and the credit cost each carry information; only minor tightening would improve it.

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 two-parameter read-only tool with no output schema, the definition covers what is returned (tokens, values, percentages) and the cost per call, which is enough to invoke it correctly. Only secondary details — result size limits or error handling — are absent.

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%, and the schema already documents both parameters, including the YYYY-MM-DD pattern and the 'one address per call'/maxItems=1 constraint. The description's 'per address' phrasing reinforces the address cardinality but adds no format or semantic detail beyond what the schema supplies.

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 aggregated token distribution across all chains') and enumerates the returned content: tokens held, their values, and percentage breakdown. It is clear what the tool does, but it never distinguishes itself from related siblings like octav_get_portfolio or octav_get_historical, so an agent must infer which one fits.

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?

Usage is only implied: the cross-chain, token-level distribution framing suggests when it fits, and the credit note signals a per-address cost constraint. There is no explicit when-to-use versus when-not, and no alternative tool is named for getting a plain portfolio value or a historical snapshot.

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