Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Sync Transactions

octav_sync_transactions

Trigger immediate transaction synchronization for a single wallet address to index its latest transactions on demand.

Instructions

Manually trigger transaction synchronization for one address. Forces immediate indexing of latest transactions. Costs 1 credit, plus 1 credit per 250 transactions indexed.

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

Input Schema

NameRequiredDescriptionDefault
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=false, destructiveHint=false, and openWorldHint=true, so the description's real contribution is the credit cost model: 1 credit plus 1 credit per 250 transactions indexed. That is genuinely decision-relevant information an agent would otherwise lack. It stops short of saying whether indexing is synchronous, how long it takes, or whether it is a no-op when data is already current.

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 no filler: action and scope first, effect second, cost last. The cost sentence earns its place because it changes the agent's willingness to call the tool.

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 one-parameter, side-effecting trigger with no output schema, the definition covers what it does, what it costs, and which address formats are accepted. The main remaining gap is the return value and whether the call blocks until indexing completes, which matters for a sync trigger.

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% and the schema already documents the array-of-one constraint, address formats, and the API's one-address-per-call limit. The description's "for one address" merely restates that, adding no format or validation detail beyond the schema, so the baseline 3 applies.

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?

"Manually trigger transaction synchronization for one address" names a specific action and resource, and "Forces immediate indexing" clarifies the effect beyond the tool name. It implicitly contrasts with passive retrieval (e.g. octav_get_transactions) but never names the sibling, so the distinction is inferred rather than stated.

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 word "Manually" implies this is the on-demand alternative to normal background sync, and "Forces immediate indexing" hints at the use case of needing fresh data now. However, there is no explicit when-not-to-use guidance, no statement of what to call instead for already-indexed data, and no note on whether repeated calls are wasteful.

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