Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Historical Portfolio

octav_get_historical
Read-only

Retrieve a wallet's portfolio snapshot for a specific past date to view holdings and values at that point in time.

Instructions

Get portfolio snapshot for a specific date in the past. Shows holdings and values at that point in time. 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_historical"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate for historical 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.8/5.0
Behavior4/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 a genuinely useful behavioral fact beyond them: 'Costs 1 credit per address,' which lets an agent weigh cost before calling. It stops short of covering invalid/future-date behavior or what the payload shape 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 with zero filler, front-loaded with the core action and followed by the output content and the cost. Nothing repeats the name or the schema.

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 tool with full schema coverage, complete parameter documentation, and annotations covering safety, this is close to sufficient. The only real gaps are practical boundaries such as the earliest supported date or how a future/invalid date is handled, which an agent might reasonably want before calling.

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%: the date pattern (YYYY-MM-DD) and the single-address array constraint with EVM/Solana formats are fully documented in the schema. The description contributes only the credit-per-address framing, which mildly reinforces the one-address limit but adds no new syntax or format meaning. 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?

The description states a specific verb and resource ('Get portfolio snapshot') plus the distinguishing scope ('for a specific date in the past') and what the result contains ('holdings and values at that point in time'). This separates it conceptually from a current-portfolio call and a block-based call, though it never names those siblings explicitly.

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 phrase 'for a specific date in the past' implies this is the date-based alternative to a live portfolio read, but there is no explicit when-to-use guidance, no exclusion of future dates, and no named alternative for current or block-height snapshots. Usage is inferable but not stated.

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