Skip to main content
Glama
alamedaim-apps

Authorize.net MCP Server

get_settled_batch_list

Retrieve settled payment batches within a specified date range to access batch IDs, settlement dates, and transaction statistics for reconciliation and reporting purposes.

Instructions

Get a list of settled batches within a date range. Returns batch IDs, settlement dates, and statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstSettlementDateNoStart date for the batch list (ISO 8601 format, e.g., 2024-01-01). Defaults to 30 days ago.
lastSettlementDateNoEnd date for the batch list (ISO 8601 format). Defaults to today.

Implementation Reference

  • The main handler function that executes the Authorize.Net API call to retrieve the list of settled batches within the specified date range using GetSettledBatchListController.
    async function getSettledBatchList(firstSettlementDate?: string, lastSettlementDate?: string) {
      const request = new ApiContracts.GetSettledBatchListRequest();
      request.setMerchantAuthentication(getMerchantAuth());
      request.setIncludeStatistics(true);
    
      if (firstSettlementDate) {
        request.setFirstSettlementDate(new Date(firstSettlementDate));
      }
      if (lastSettlementDate) {
        request.setLastSettlementDate(new Date(lastSettlementDate));
      }
    
      const ctrl = new ApiControllers.GetSettledBatchListController(request.getJSON());
      const response = await executeController(ctrl);
    
      const apiResponse = new ApiContracts.GetSettledBatchListResponse(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.getBatchList() || [];
    }
  • src/index.ts:200-216 (registration)
    Registration of the tool in the MCP server's ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: "get_settled_batch_list",
      description: "Get a list of settled batches within a date range. Returns batch IDs, settlement dates, and statistics.",
      inputSchema: {
        type: "object",
        properties: {
          firstSettlementDate: {
            type: "string",
            description: "Start date for the batch list (ISO 8601 format, e.g., 2024-01-01). Defaults to 30 days ago.",
          },
          lastSettlementDate: {
            type: "string",
            description: "End date for the batch list (ISO 8601 format). Defaults to today.",
          },
        },
      },
    },
  • src/index.ts:301-306 (registration)
    Dispatch to the getSettledBatchList handler within the MCP server's CallToolRequestSchema handler.
    case "get_settled_batch_list":
      result = await getSettledBatchList(
        args?.firstSettlementDate as string | undefined,
        args?.lastSettlementDate as string | undefined
      );
      break;
  • Input schema definition for the get_settled_batch_list tool.
    inputSchema: {
      type: "object",
      properties: {
        firstSettlementDate: {
          type: "string",
          description: "Start date for the batch list (ISO 8601 format, e.g., 2024-01-01). Defaults to 30 days ago.",
        },
        lastSettlementDate: {
          type: "string",
          description: "End date for the batch list (ISO 8601 format). Defaults to today.",
        },
      },
    },
  • Helper function used by the handler to execute Authorize.Net API controllers asynchronously.
    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 the tool returns batch IDs, settlement dates, and statistics, but doesn't cover important aspects like whether this is a read-only operation, pagination behavior, rate limits, authentication requirements, or error handling. The description is minimal and lacks behavioral context beyond basic output.

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 extremely concise with just two sentences that efficiently communicate the core functionality. The first sentence states what the tool does, and the second specifies what information is returned. There's zero wasted language, and it's appropriately sized for this simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with 2 well-documented parameters and no output schema, the description is minimally adequate. It covers the basic purpose and return values, but given the lack of annotations and output schema, it should ideally provide more behavioral context about the operation's characteristics and limitations.

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 description mentions 'within a date range' which aligns with the two parameters in the schema. Since schema description coverage is 100% (both parameters have good descriptions with format examples and defaults), the description adds minimal value beyond what the schema already provides. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('list of settled batches'), including what information is returned. It distinguishes from some siblings like 'get_unsettled_transaction_list' by specifying 'settled' batches, but doesn't explicitly differentiate from all siblings like 'get_batch_statistics'.

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 when to choose this over 'get_batch_statistics' or 'get_transaction_list', nor does it specify prerequisites or exclusions. The date range context is implied but not framed as usage guidance.

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