Skip to main content
Glama
Octav-Labs

Octav API MCP Server

Official
by Octav-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Transaction History

octav_get_transactions
Read-only

Query wallet transaction history with filters for chain, type, protocol, counterparty, date range, and token ID; paginate results and hide spam or dust.

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.

Input Schema

NameRequiredDescriptionDefault
sortNoSort by timestamp (default: DESC, newest first)
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 of wallet addresses (EVM: 0x... or Solana base58). Max 10 addresses.
startDateNoStart date for filtering (YYYY-MM-DD)
interactingAddressesNoOnly transactions with these counterparty addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)"
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=true), and the description adds genuinely non-derivable facts: a 250-transaction per-request cap and a per-address credit cost. It omits whether stale data requires a preliminary sync or what the response 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with purpose and followed by capabilities then hard constraints (limit, cost). The filter enumeration partially restates the schema, but it is compact enough to aid scanning rather than bloat.

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 14-parameter read tool with full schema coverage, existing annotations, and no output schema, the description supplies the operational constraints an agent needs (rate/cost, page cap) and the filter surface. The remaining gap is workflow context — whether a sync step is required first — which keeps it from a 5.

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 schema. The description's enumeration of filter dimensions (chain, type, protocol, counterparty, search, NFT token ID, dates, spam/dust) maps onto those parameters without adding syntax, defaults, or cross-field guidance, which is the baseline-3 case.

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 ('Query transaction history') plus two capabilities ('filtering and pagination'), which clearly separates it from octav_sync_transactions, the write-side counterpart in the sibling list. It stops short of explicitly naming that sibling, so the differentiation is inferable 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?

Conveys useful operating context (max 250 per request, 1 credit per address) but never says when to use this versus octav_sync_transactions or octav_get_portfolio, nor any prerequisite such as whether history must be synced first. Usage is implied by the tool name and filters only.

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

Deploy Server

Other Tools