Skip to main content
Glama
Jake-loranger

Algorand MCP Server

get_transaction

Retrieve detailed information about specific transactions on the Algorand blockchain by providing the transaction ID.

Instructions

Get transaction details by transaction ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txIdYesTransaction ID

Implementation Reference

  • Main handler for the 'get_transaction' tool: parses arguments using Zod schema, fetches transaction via algorandService, returns formatted JSON response or error.
    case 'get_transaction': {
        const parsed = GetTransactionArgsSchema.parse(args);
        try {
            const txInfo = await algorandService.getTransaction(parsed.txId);
            return {
                content: [
                    {
                        type: 'text',
                        text: `Transaction Information:\n${JSON.stringify(txInfo, null, 2)}`,
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error getting transaction: ${error}`,
                    },
                ],
                isError: true,
            };
        }
    }
  • Zod schema defining input validation for get_transaction tool arguments (txId: string).
    const GetTransactionArgsSchema = z.object({
        txId: z.string(),
    });
  • src/index.ts:309-322 (registration)
    MCP tool registration entry defining name, description, and input schema for 'get_transaction'.
    {
        name: 'get_transaction',
        description: 'Get transaction details by transaction ID',
        inputSchema: {
            type: 'object',
            properties: {
                txId: {
                    type: 'string',
                    description: 'Transaction ID',
                },
            },
            required: ['txId'],
        },
    },
  • Supporting method in AlgorandService that retrieves transaction information using algodClient.pendingTransactionInformation.
    async getTransaction(txId: string) {
        try {
            const txInfo = await this.algodClient.pendingTransactionInformation(txId).do();
            return txInfo;
        } catch (error) {
            throw new Error(`Failed to get transaction: ${error}`);
        }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Get transaction details' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, potential rate limits, error conditions (e.g., invalid ID), or what the return format looks like. This leaves significant gaps for an agent to understand how to use it effectively.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information.

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

Completeness2/5

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

Given the complexity of a transaction retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'details' include (e.g., fields returned), error handling, or behavioral context. For a tool that likely returns structured data, more completeness is needed to guide an agent effectively.

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?

The schema description coverage is 100%, with the parameter 'txId' fully documented in the schema as 'Transaction ID'. The description adds no additional meaning beyond this, as it only restates 'by transaction ID'. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the verb 'Get' and the resource 'transaction details', specifying it's done 'by transaction ID'. It distinguishes from siblings like 'get_account_info' or 'get_asset_info' by focusing on transactions. However, it doesn't explicitly mention what details are retrieved (e.g., amount, status, timestamp), keeping it at 4 rather than 5.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this is for retrieving a single transaction's metadata versus using other tools for broader operations like 'send_payment' or 'transfer_asset'. The description only states what it does, not when it's appropriate.

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/Jake-loranger/algorand-mcp-server'

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