Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_get_transaction

Retrieve transaction details by ID to view payment information, verify status, and access records for charges, refunds, or payouts.

Instructions

Retrieve a transaction by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTransaction ID

Implementation Reference

  • Handler implementation for the 'vaultix_get_transaction' tool. It retrieves a transaction by ID via a GET request to `/transactions/${args.id}` using the VaultixClient.
    case 'vaultix_get_transaction':
      return client.get(`/transactions/${args.id}`)
  • Input schema definition for the 'vaultix_get_transaction' tool, specifying the required 'id' parameter as a string.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Transaction ID' },
      },
      required: ['id'],
    },
  • Registration of the 'vaultix_get_transaction' tool in the exported tools array, including name, description, and input schema.
    {
      name: 'vaultix_get_transaction',
      description: 'Retrieve a transaction by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Transaction ID' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Retrieve' implies a read operation, but it doesn't specify authentication requirements, rate limits, error conditions, or what data is returned. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise at just four words, front-loading the essential information with zero wasted words. Every element ('Retrieve', 'transaction', 'by ID') serves a clear purpose in communicating the tool's function.

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 read operation with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'transaction' represents in this context, what fields are returned, or how this differs from similar retrieval tools. The minimal description leaves too many contextual questions unanswered.

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 input schema has 100% description coverage, with the single parameter 'id' clearly documented as 'Transaction ID'. The description doesn't add any additional parameter information beyond what the schema provides, which is acceptable given the high schema coverage.

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 action ('Retrieve') and resource ('a transaction by ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'vaultix_get_charge' or 'vaultix_get_payout' which follow the same pattern, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'vaultix_get_transactions_summary' and 'vaultix_list_transactions' available, there's no indication of when a single transaction lookup is preferred over summary or list operations.

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/VautlixDevelopment/mcpVaultix'

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