Skip to main content
Glama

get_transaction

Retrieve detailed information about a specific cryptocurrency transaction using its ID. This tool provides transaction details including amounts, with optional currency conversion and wallet context for multi-wallet sessions.

Instructions

Get details of a specific transaction by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transaction_idYesTransaction ID to retrieve
display_currencyNoDisplay currency for amount conversion (e.g. KRW, EUR). Defaults to server setting.
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • The handler function 'registerGetTransaction' defines the 'get_transaction' tool, sets up its input schema, and implements the logic by calling the API client to fetch transaction details.
    export function registerGetTransaction(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
      server.tool(
        'get_transaction',
        withWalletPrefix('Get details of a specific transaction by ID.', walletContext?.walletName),
        {
          transaction_id: z.string().describe('Transaction ID to retrieve'),
          display_currency: z.string().optional().describe('Display currency for amount conversion (e.g. KRW, EUR). Defaults to server setting.'),
          wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
        },
        async (args) => {
          const params = new URLSearchParams();
          if (args.display_currency) params.set('display_currency', args.display_currency);
          if (args.wallet_id) params.set('walletId', args.wallet_id);
          const qs = params.toString();
          const result = await apiClient.get(`/v1/transactions/${args.transaction_id}${qs ? '?' + qs : ''}`);
          return toToolResult(result);
        },
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description lacks critical context: error handling for invalid IDs, whether the returned data includes raw blockchain data or processed views, and the implications of the multi-wallet session logic mentioned in the schema.

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?

Extremely concise at nine words in a single sentence. The structure is front-loaded with the action verb. However, the brevity leaves insufficient room for explaining the business logic embedded in the optional parameters (currency conversion, wallet resolution), suggesting it may be overly terse rather than efficiently complete.

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?

For a tool with three parameters and specific wallet-resolution logic, the description is incomplete. It fails to clarify that 'display_currency' performs real-time conversion or explain the multi-wallet session behavior referenced in the wallet_id schema description. No output schema exists, yet the description offers no hint about what transaction details are returned.

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%, with all three parameters (transaction_id, display_currency, wallet_id) fully documented in the JSON schema. The description adds no parameter-specific guidance beyond the schema, earning the baseline score for high-coverage schemas.

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 uses a specific verb ('Get') with clear resource ('details of a specific transaction') and scope ('by ID'). However, it does not explicitly distinguish from sibling 'list_transactions', which likely returns multiple transactions versus this single-record retrieval.

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 provided on when to use this tool versus 'list_transactions' or other retrieval options. The description does not explain the optional 'display_currency' use case (viewing amounts in different currencies) or when 'wallet_id' is required versus auto-resolved.

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/minhoyoo-iotrust/WAIaaS'

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