Skip to main content
Glama
vechain

VeChain MCP Server

Official
by vechain

Indexer: Transactions for a contract (v1)

getContractTransactions
Read-only

Retrieve paginated transaction history for a given contract address on VeChain, with optional time range filters and expanded details.

Instructions

Query VeWorld Indexer /api/v1/transactions/contract for transactions interacting with a contract address. Supports pagination.

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
afterNoReturn txs at or after this Unix timestamp (seconds)
beforeNoReturn txs at or before this Unix timestamp (seconds)
cursorNoOpaque cursor for fetching the next page when provided by the API
expandedNoInclude decoded clause outputs/logs for richer results, would recommend to set to true to get the full transaction details
directionNoSort direction for time-based queries; defaults to 'DESC' (newest first)
contractAddressYesContract address that the transaction interacted with

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNoList response for transactions endpoints
errorNo
networkYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds only that it queries a specific API and supports pagination, which is already implicit. No contradictions, but minimal added value beyond annotations.

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?

Two sentences, no filler, front-loaded with the core action. Every word earns its place.

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?

Given the presence of an output schema and fully annotated parameters, the description is adequate for a read-only paginated query. Could optionally mention rate limits or result trimming, but not essential.

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?

All 8 parameters have descriptions in the schema (100% coverage), so the description adds no additional meaning beyond stating pagination support. Baseline 3 is appropriate.

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 verb 'Query' and the resource 'transactions for a contract', including the specific API endpoint. This distinguishes it from sibling tools like getTransactions (general) and getTransfersFrom.

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 description implies usage for contract transactions but provides no explicit guidance on when to use this tool versus alternatives such as getTransactions or getTransfersFrom.

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