Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_payment_integration_provider_create

Create a white-label payment integration provider for Authorize.net or NMI by supplying required details, so a location can add and manage its payment setup.

Instructions

Create White-label Integration Provider The "Create White-label Integration Provider" API allows adding a new payment provider integration to the system which is built on top of Authorize.net or NMI. Use this endpoint to create a integration provider with the specified details. Ensure that the required information is provided in the request payload. This endpoint can be only invoked using marketplace-app token Endpoint: POST /payments/integrations/provider/whitelabel (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/integration.write

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "ghl_payment_integration_provider_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateWhiteLabelIntegrationProviderDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds real context beyond them: the endpoint path/version header, the marketplace-app-token-only restriction, and the sub-account token requirement — all actionable call constraints an agent would otherwise miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the auth/endpoint lines earn their place, but the title is repeated verbatim as the first line and 'Use this endpoint to create a integration provider with the specified details. Ensure that the required information is provided' is filler that adds nothing.

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?

For a mutation tool with a nested body and no output schema, the description covers auth model, endpoint, and provider constraint adequately. It doesn't say whether the created provider returns credentials or configuration state, which is the main remaining ambiguity.

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 coverage is 100% and the nested body documents all seven fields with examples, so the schema carries the semantics. The description only adds the platform constraint (Authorize.net or NMI) that gives meaning to the provider enum; it says nothing about altId/altType or uniqueName behavior beyond 'provide required information'.

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 states a specific verb and resource ('adding a new payment provider integration') and qualifiers that matter: it is a white-label provider built on Authorize.net or NMI. That qualifier implicitly separates it from ghl_payment_custom_provider_create, though no sibling is named explicitly.

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?

It gives prerequisites (marketplace-app token only, sub-account/location token, OAuth scope payments/integration.write) but the 'when to use' sentence is a restatement ('Use this endpoint to create a integration provider with the specified details'). No exclusion or alternative, e.g. custom provider vs white-label provider, is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools