Skip to main content
Glama
alamedaim-apps

Authorize.net MCP Server

get_unsettled_transaction_list

Retrieve pending Authorize.net transactions awaiting settlement to monitor unbatched payments and track pending revenue.

Instructions

Get all transactions that are pending settlement (not yet batched).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_unsettled_transaction_list' tool. It constructs an AuthorizeNet API request, authenticates with merchant credentials, executes the GetUnsettledTransactionListController via the executeController helper, handles errors, and returns the list of unsettled transactions.
    async function getUnsettledTransactionList() {
      const request = new ApiContracts.GetUnsettledTransactionListRequest();
      request.setMerchantAuthentication(getMerchantAuth());
    
      const ctrl = new ApiControllers.GetUnsettledTransactionListController(request.getJSON());
      const response = await executeController(ctrl);
    
      const apiResponse = new ApiContracts.GetUnsettledTransactionListResponse(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.getTransactions() || [];
    }
  • Tool specification including name, description, and input schema (empty object as no parameters are required). This is returned by the ListTools handler.
    {
      name: "get_unsettled_transaction_list",
      description: "Get all transactions that are pending settlement (not yet batched).",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:312-314 (registration)
    Registration/dispatch logic in the CallTool request handler switch statement, which invokes the handler function when the tool is called.
    case "get_unsettled_transaction_list":
      result = await getUnsettledTransactionList();
      break;
  • Helper function used by all tool handlers, including getUnsettledTransactionList, to execute AuthorizeNet controllers asynchronously with proper environment setting and error handling.
    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);
          }
        });
      });
    }
  • Helper function to create merchant authentication object using environment variables, used by all API requests including this tool.
    function getMerchantAuth() {
      const merchantAuth = new ApiContracts.MerchantAuthenticationType();
      merchantAuth.setName(API_LOGIN_ID);
      merchantAuth.setTransactionKey(TRANSACTION_KEY);
      return merchantAuth;
    }
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. It states the tool retrieves data ('Get'), implying a read-only operation, but lacks details on permissions, rate limits, pagination, or response format. This is a significant gap for a tool with zero annotation coverage.

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 with zero waste. It is front-loaded with the core purpose and includes clarifying parenthetical context ('not yet batched'). Every word earns its place.

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 no annotations, no output schema, and a read-focused tool, the description is incomplete. It lacks behavioral context (e.g., response format, error handling) and doesn't clarify scope (e.g., date ranges, limits). For a tool with zero structured data, more guidance is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter information, focusing on the tool's purpose instead. Baseline is 4 for zero parameters.

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 resource ('transactions that are pending settlement'), specifying the exact subset of transactions. It distinguishes from siblings like 'get_settled_batch_list' by focusing on unsettled transactions, though it doesn't explicitly name alternatives.

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?

The description implies usage when needing pending/unsettled transactions, but provides no explicit guidance on when to use this tool versus alternatives like 'get_transaction_list' or 'get_settled_batch_list'. No exclusions or prerequisites are mentioned.

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