Skip to main content
Glama
alamedaim-apps

Authorize.net MCP Server

get_transaction_details

Retrieve complete transaction information using the transaction ID to view payment details, status, and history from Authorize.net.

Instructions

Get full details for a specific transaction by its transaction ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionIdYesThe transaction ID to retrieve details for.

Implementation Reference

  • The main handler function for the 'get_transaction_details' tool. It constructs a GetTransactionDetailsRequest, authenticates with merchant credentials, executes the Authorize.Net API call via controller, handles errors, and returns the transaction details.
    async function getTransactionDetails(transactionId: string) {
      const request = new ApiContracts.GetTransactionDetailsRequest();
      request.setMerchantAuthentication(getMerchantAuth());
      request.setTransId(transactionId);
    
      const ctrl = new ApiControllers.GetTransactionDetailsController(request.getJSON());
      const response = await executeController(ctrl);
    
      const apiResponse = new ApiContracts.GetTransactionDetailsResponse(response);
      if (apiResponse.getMessages().getResultCode() !== ApiContracts.MessageTypeEnum.OK) {
        const errors = apiResponse.getMessages().getMessage();
        throw new Error(`API Error: ${errors[0].getCode()} - ${errors[0].getText()}`);
      }
    
      return apiResponse.getTransaction();
    }
  • src/index.ts:253-266 (registration)
    Registers the 'get_transaction_details' tool in the ListTools response, including its name, description, and input schema definition.
    {
      name: "get_transaction_details",
      description: "Get full details for a specific transaction by its transaction ID.",
      inputSchema: {
        type: "object",
        properties: {
          transactionId: {
            type: "string",
            description: "The transaction ID to retrieve details for.",
          },
        },
        required: ["transactionId"],
      },
    },
  • Defines the input schema for the 'get_transaction_details' tool, specifying the required 'transactionId' parameter.
    inputSchema: {
      type: "object",
      properties: {
        transactionId: {
          type: "string",
          description: "The transaction ID to retrieve details for.",
        },
      },
      required: ["transactionId"],
    },
  • src/index.ts:320-322 (registration)
    Dispatches execution of the 'get_transaction_details' tool in the CallToolRequest handler by calling the handler function.
    case "get_transaction_details":
      result = await getTransactionDetails(args?.transactionId as string);
      break;
  • Shared utility function used by all tools, including 'get_transaction_details', to asynchronously execute Authorize.Net API controllers.
    function executeController(ctrl: any): Promise<any> {
      return new Promise((resolve, reject) => {
        if (ENVIRONMENT === "production") {
          ctrl.setEnvironment(SDKConstants.endpoint.production);
        }
        ctrl.execute(() => {
          const response = ctrl.getResponse();
          if (response === null) {
            reject(new Error(ctrl.getErrorResponse() || "No response from API"));
          } else {
            resolve(response);
          }
        });
      });
    }
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. It states this is a read operation ('Get'), but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'full details' entails (e.g., format, included fields). This leaves significant gaps for a tool that retrieves transaction data.

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 front-loads the core action ('Get full details') without unnecessary words. It directly addresses the tool's function, making it easy to parse and understand quickly.

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 transaction data retrieval, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'full details' includes, potential response formats, or behavioral traits like idempotency or error cases. This is inadequate for a tool that likely returns structured financial data.

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 'transactionId' fully documented in the schema. The description adds no additional semantic context beyond implying it's for a 'specific transaction', which the schema already covers. This meets the baseline for 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 verb ('Get full details') and resource ('for a specific transaction'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_transaction_list' or 'get_unsettled_transaction_list', which likely provide different scopes of transaction data.

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. It doesn't mention prerequisites, context for selecting this over sibling tools (e.g., 'get_transaction_list' for summaries vs. this for details), or any exclusions. Usage is implied but not explicitly stated.

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/alamedaim-apps/authnet-mcp'

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