Skip to main content
Glama
vechain

VeChain MCP Server

Official
by vechain

Get History of account

getHistoryOfAccount
Read-only

Retrieve transaction history for a VeChain address with filters for event types, time range, and address roles. Supports staking, transfers, swaps, governance, and more.

Instructions

Retrieve transaction history for a VeChain address with filtering support.

IMPORTANT: Pass ARRAYS of event names to fetch multiple event types in ONE call - this is much more efficient than separate calls.

Available Event Types:

STARGATE STAKING (Current - Post-Hayabusa):

  • STARGATE_STAKE: User stakes VET and mints Stargate NFT

  • STARGATE_UNSTAKE: User unstakes VET and burns NFT

  • STARGATE_DELEGATE_REQUEST: User requests to delegate NFT to validator

  • STARGATE_DELEGATE_ACTIVE: Delegation becomes active with validator

  • STARGATE_DELEGATE_EXIT_REQUEST: User requests to exit delegation

  • STARGATE_DELEGATION_EXITED: Delegation fully exited, can unstake

  • STARGATE_DELEGATION_EXITED_VALIDATOR: Validator-side exit event

  • STARGATE_DELEGATE_REQUEST_CANCELLED: Delegation request cancelled before activation

  • STARGATE_CLAIM_REWARDS: User claims VTHO staking rewards

  • STARGATE_BOOST: User boosts NFT maturity with VTHO payment

  • STARGATE_MANAGER_ADDED: User adds manager address to control NFT

  • STARGATE_MANAGER_REMOVED: Manager address removed from NFT

STARGATE LEGACY (Pre-Hayabusa - Historical only):

  • STARGATE_DELEGATE_LEGACY: Old delegation system

  • STARGATE_CLAIM_REWARDS_BASE_LEGACY: Old base rewards

  • STARGATE_CLAIM_REWARDS_DELEGATE_LEGACY: Old delegation rewards

  • STARGATE_UNDELEGATE_LEGACY: Old undelegation

TRANSFERS:

  • TRANSFER_VET: Native VET token transfers

  • TRANSFER_FT: Fungible token (VIP-180) transfers - includes VTHO, other tokens

  • TRANSFER_NFT: NFT (VIP-181/VIP-721) transfers

  • TRANSFER_SF: Semi-fungible token transfers

SWAPS (DEX Activity):

  • SWAP_VET_TO_FT: Swapping VET for tokens

  • SWAP_FT_TO_VET: Swapping tokens for VET

  • SWAP_FT_TO_FT: Token-to-token swaps

VEBETTERDAO (B3TR Ecosystem):

  • B3TR_SWAP_VOT3_TO_B3TR: Converting VOT3 governance token to B3TR

  • B3TR_SWAP_B3TR_TO_VOT3: Converting B3TR to VOT3

  • B3TR_PROPOSAL_SUPPORT: Supporting a proposal with B3TR

  • B3TR_PROPOSAL_VOTE: Voting on governance proposal

  • B3TR_PROPOSAL_WITHDRAW: Withdrawing a B3TR proposal

  • B3TR_XALLOCATION_VOTE: Voting on X-Allocation distribution

  • B3TR_CLAIM_REWARD: Claiming B3TR ecosystem rewards

  • B3TR_UPGRADE_GM: Upgrading governance model

  • B3TR_ACTION: General B3TR ecosystem action

GOVERNANCE:

  • VEVOTE_VOTE_CAST: Vote cast in VeVote governance system

OTHER:

  • NFT_SALE: NFT marketplace sale transaction

  • UNKNOWN_TX: Unclassified transaction type

Common Query Patterns:

Complete Stargate history: ["STARGATE_STAKE", "STARGATE_UNSTAKE", "STARGATE_DELEGATE_REQUEST", "STARGATE_DELEGATE_ACTIVE", "STARGATE_DELEGATE_EXIT_REQUEST", "STARGATE_DELEGATION_EXITED", "STARGATE_CLAIM_REWARDS", "STARGATE_BOOST", "STARGATE_MANAGER_ADDED", "STARGATE_MANAGER_REMOVED"]

All asset transfers: ["TRANSFER_VET", "TRANSFER_FT", "TRANSFER_NFT", "TRANSFER_SF"]

Trading activity: ["SWAP_VET_TO_FT", "SWAP_FT_TO_VET", "SWAP_FT_TO_FT"]

Filters:

  • eventName: Single string OR array (ALWAYS prefer arrays for related events)

  • searchBy: 'to' | 'from' | 'origin' | 'gasPayer' - filter by address role

  • contractAddress: Filter by specific contract interactions

  • after/before: Unix timestamps in SECONDS (NOT milliseconds). Example: 2025-08-03 00:00 UTC = 1754179200, 2025-08-04 00:00 UTC = 1754265600

  • Pagination: page, size, cursor, direction (ASC/DESC)

Returns paginated array of events with full transaction details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based results page number (0 is the first page)
sizeNoResults per page (1..150); API default is typically 20
afterNoOptional filter by after timestamp (Unix seconds, e.g. 1754179200 for 2025-08-03T00:00:00Z). Use seconds, NOT milliseconds.
beforeNoOptional filter by before timestamp (Unix seconds, e.g. 1754265600 for 2025-08-04T00:00:00Z). Use seconds, NOT milliseconds.
cursorNoOpaque cursor for fetching the next page when provided by the API
addressYesThe account address or VNS (.vet) name to retrieve
searchByNoOptional filter by search by (to, from, origin, gasPayer)
directionNoSort direction for time-based queries; defaults to 'DESC' (newest first)
eventNameNoOptional filter by event name(s). Can be a single event or an array of events
contractAddressNoOptional filter by contract address

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo
networkYes
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains the efficiency of array usage, pagination behavior, timestamp format (seconds vs milliseconds), and the purpose of each filter. Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is well-structured with headings and bullet points, but it is very long and includes redundant examples (e.g., full event type lists repeated in query patterns). It could be more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, 1 required, many enums, output schema present), the description covers all facets: filters, pagination, event types, and usage patterns. It is thorough and leaves no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning by explaining timestamp formats, common query patterns, and how to combine parameters. It provides examples that go beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the purpose: 'Retrieve transaction history for a VeChain address with filtering support.' It uses a specific verb and resource, and distinguishes this tool from siblings like getTransactions or getTransfersOfAccount by focusing on account-specific history with extensive event type filtering.

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

Usage Guidelines4/5

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

The description provides explicit guidance on using arrays for event names to improve efficiency, and includes common query patterns. However, it does not explicitly compare to sibling tools or state when to use this tool over alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vechain/vechain-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server