Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Subscribe to Snapshots

octav_subscribe_snapshot

Subscribe wallet addresses to automatic portfolio snapshots for historical tracking. Track portfolio value over time across blockchains using the Octav API; costs 1200 credits.

Instructions

Subscribe to automatic portfolio snapshots. Enables historical tracking. Costs 1200 credits. API expects addresses with optional descriptions.

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_subscribe_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesArray of wallet addresses (EVM: 0x... or Solana base58).
descriptionNoOptional description for the subscription

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 of wallet addresses (EVM: 0x... or Solana base58)."
    • removedInput schema / properties / addresses / maxItems
      Removed value: -10
  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 declare a non-read-only, non-destructive, open-world operation, so the mutation profile is covered. The description adds genuinely useful context beyond that: a concrete cost of 1200 credits, which matters for a paid mutation. However, it omits what an agent most needs for this operation — snapshot frequency, whether duplicate subscriptions are rejected, whether it can be cancelled, and what is returned on success.

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 purpose and outcome, with the cost disclosed early. The final sentence about addresses and descriptions is largely redundant with the schema and could be dropped without loss.

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 subscription tool with no output schema, the definition covers purpose, cost, and the shape of input. It is somewhat thin on lifecycle details (frequency, cancellation, idempotency) that would matter for a paid recurring subscription, but nothing required to invoke it is missing.

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 address formats (EVM 0x or Solana base58) and the optional description field. The sentence 'API expects addresses with optional descriptions' only restates the schema, adding no new semantics such as batching limits or address validation behavior.

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 ('Subscribe to automatic portfolio snapshots') plus the outcome ('Enables historical tracking'), so an agent knows this sets up recurring snapshot capture rather than fetching data. It does not name or contrast with related read tools like octav_get_historical, so sibling differentiation is only implicit.

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 'Enables historical tracking' implies the use case (you want an ongoing record, not a one-off read), but there is no explicit when-to-use statement, no exclusion of alternatives, and no prerequisite guidance such as whether addresses must already be known to the system.

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