Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Transaction History

octav_get_transactions
Read-only

Query and filter wallet transaction history by chain, type, protocol, counterparty, date, NFT token ID, and spam/dust; paginate up to 250 results per request.

Instructions

Query transaction history with filtering and pagination. Filter by chain, type, protocol, counterparty, text search, NFT token ID, and date range, and hide spam or dust. Max 250 transactions per request. 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_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by timestamp (default: NEWEST)
typeNoFilter by transaction types, comma-separated (e.g., SWAP,DEPOSIT)
chainNoFilter by chain keys, comma-separated (e.g., ethereum,arbitrum,base). See octav_get_chains.
limitNoNumber of transactions to return (default: 50, max: 250)
offsetNoPagination offset (default: 0)
searchNoFull-text search over token symbols, names and addresses
endDateNoEnd date for filtering (YYYY-MM-DD)
tokenIdNoFilter by NFT token ID
hideDustNoExclude dust transactions
hideSpamNoExclude spam transactions
protocolNoFilter by protocol keys, comma-separated. See octav_get_chain_protocols.
addressesYesArray with one wallet address (EVM: 0x... or Solana base58). The API accepts one address per call.
startDateNoStart date for filtering (YYYY-MM-DD)
interactingAddressesNoOnly transactions with these counterparty addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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
    • changedInput schema / properties / sort / description
      Previous value: -"Sort by timestamp (default: DESC, newest first)"New value: +"Sort by timestamp (default: NEWEST)"
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "ASC",
      -  "DESC"
      -]New value: +[
      +  "NEWEST",
      +  "OLDEST"
      +]
  2. Changed9 schema fields changedv1.2.1
    • changedInput schema / properties / chain / description
      Previous value: -"Filter by specific chain (e.g., ethereum, solana, arbitrum)"New value: +"Filter by chain keys, comma-separated (e.g., ethereum,arbitrum,base). See octav_get_chains."
    • addedInput schema / properties / hideDust
      Added value: +{
      +  "description": "Exclude dust transactions",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hideSpam
      Added value: +{
      +  "description": "Exclude spam transactions",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / interactingAddresses
      Added value: +{
      +  "description": "Only transactions with these counterparty addresses",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / protocol
      Added value: +{
      +  "description": "Filter by protocol keys, comma-separated. See octav_get_chain_protocols.",
      +  "type": "string"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Full-text search over token symbols, names and addresses",
      +  "type": "string"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort by timestamp (default: DESC, newest first)",
      +  "enum": [
      +    "ASC",
      +    "DESC"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tokenId
      Added value: +{
      +  "description": "Filter by NFT token ID",
      +  "type": "string"
      +}
    • changedInput schema / properties / type / description
      Previous value: -"Filter by transaction type (e.g., transfer, swap, stake)"New value: +"Filter by transaction types, comma-separated (e.g., SWAP,DEPOSIT)"
  3. First observedv1.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful operational context beyond annotations: 'Max 250 transactions per request' and 'Costs 1 credit per address', which lets an agent budget calls and set limits. It does not describe what a returned transaction record contains, which keeps this from a 5.

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 tight sentences, front-loaded with purpose, then capability scope, then limits and cost. The middle sentence listing filters partially duplicates the schema's parameter descriptions, which is the only wasted weight; the limit and credit lines are well placed where an agent will see them.

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?

For a 14-parameter tool with no output schema, the description covers the volume cap and credit cost well but omits what a result actually contains and whether a prior sync is required. Those are the two facts an agent most needs before committing credits to a call. Adequate but with clear gaps.

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%, so every one of the 14 parameters is already documented in the input schema, including enums and the single-address maxItems constraint. The description's filter enumeration (chain, type, protocol, counterparty, text search, NFT token ID, date range, spam/dust) largely restates the schema rather than adding syntax or semantics. 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?

The description opens with a specific verb and resource: 'Query transaction history with filtering and pagination.' An agent immediately understands this is a paginated read of transaction history for an address. It stops short of naming a sibling (e.g., octav_sync_transactions for populating data, or octav_get_historical for point-in-time queries with its own chain key), so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. The description never says whether data must first be populated via octav_sync_transactions, nor how this differs from the similarly named octav_get_historical sibling. An agent must guess at prerequisites and alternative selection.

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