Skip to main content
Glama
alamedaim-apps

Authorize.net MCP Server

get_merchant_details

Retrieve merchant account information like business name, gateway ID, and payment processors from Authorize.net to verify account setup and configuration.

Instructions

Get merchant account information including name, gateway ID, and processors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the get_merchant_details tool logic: creates API request, calls controller, handles response, and returns formatted merchant details.
    async function getMerchantDetails() {
      const request = new ApiContracts.GetMerchantDetailsRequest();
      request.setMerchantAuthentication(getMerchantAuth());
    
      const ctrl = new ApiControllers.GetMerchantDetailsController(request.getJSON());
      const response = await executeController(ctrl);
    
      const apiResponse = new ApiContracts.GetMerchantDetailsResponse(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 {
        merchantName: apiResponse.getMerchantName(),
        gatewayId: apiResponse.getGatewayId(),
        processors: apiResponse.getProcessors(),
        contactDetails: apiResponse.getContactDetails(),
      };
    }
  • Tool schema definition in the ListTools response, including name, description, and input schema (no inputs required).
      name: "get_merchant_details",
      description: "Get merchant account information including name, gateway ID, and processors.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:328-330 (registration)
    Tool registration in the switch statement of the CallToolRequestSchema handler, dispatching to the getMerchantDetails function.
    case "get_merchant_details":
      result = await getMerchantDetails();
      break;
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. While 'Get' implies a read operation, it doesn't specify authentication requirements, rate limits, error conditions, or what happens when merchant data isn't found. 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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a zero-parameter tool and front-loads the essential information about what merchant data will be retrieved.

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 zero-parameter tool with no output schema, the description provides adequate but minimal information. It states what data will be retrieved but doesn't explain the return format, whether all merchant fields are always returned, or how this differs from merchant information that might be embedded in transaction data from sibling tools.

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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and it focuses on what data will be retrieved rather than how to request it.

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 ('Get') and resource ('merchant account information') with specific data fields (name, gateway ID, processors). However, it doesn't differentiate from sibling tools like get_customer_profile_transaction_list or get_transaction_details, which also retrieve merchant-related information.

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 get_transaction_details and get_transaction_list that might retrieve overlapping merchant data, there's no indication of when this specific merchant account information tool is appropriate versus those transaction-focused tools.

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