Skip to main content
Glama

get_transaction

Retrieve a specific transaction by its ID to view its full details and status.

Instructions

Get a transaction by ID. GET /transactions/{transactionId}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionIdYesTransaction ID (required)

Implementation Reference

  • Handler function that validates input with Zod schema, then calls transactionService.getTransaction to fetch the transaction.
    async function handler(client: Client, args: Record<string, unknown> | undefined) {
      const parsed = schema.safeParse(args);
      if (!parsed.success) {
        return errorResult(parsed.error.errors.map((e) => e.message).join("; "));
      }
      return handleToolCall(() =>
        transactionService.getTransaction(client, parsed.data.transactionId)
      );
    }
  • Zod schema and MCP inputSchema definition for get_transaction tool. Requires transactionId (string).
    const schema = z.object({
      transactionId: z.string().min(1, "transactionId is required"),
    });
    
    const definition = {
      name: "get_transaction",
      description: "Get a transaction by ID. GET /transactions/{transactionId}.",
      inputSchema: {
        type: "object" as const,
        properties: {
          transactionId: { type: "string", description: "Transaction ID (required)" },
        },
        required: ["transactionId"],
      },
    };
  • Export of the getTransactionTool as a Tool object combining definition and handler.
    export const getTransactionTool: Tool = {
      definition,
      handler,
    };
  • Re-export of getTransactionTool from the transactions barrel module.
    export { getTransactionTool } from "./getTransaction.js";
    export { refundTransactionTool } from "./refundTransaction.js";
    export { voidTransactionTool } from "./voidTransaction.js";
  • Service function that makes the actual HTTP GET request to /transactions/{transactionId}.
    export async function getTransaction(
      client: Client,
      transactionId: string
    ): Promise<unknown> {
      return client.get<unknown>(`/transactions/${transactionId}`);
    }
Behavior3/5

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

Uses GET which implies read-only, but no explicit mention of side effects, auth, or other behavioral traits; annotations are absent so description carries full burden but does not fully disclose.

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 short sentences, front-loaded key info, no wasted words.

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?

Adequate for simple retrieval with one param; could mention response fields but not critical.

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 provides 100% coverage with single parameter description; description adds no extra meaning beyond 'by ID', meeting baseline without improvement.

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?

Clearly states resource (transaction) and action (get by ID) with endpoint, distinguishing from list_transactions.

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?

Implies use when transaction ID is known, but lacks explicit when-to-use or alternatives; sibling names provide some context but description itself does not.

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/rhinosaas/rebillia-mcp-server'

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