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

ghl-mcp-server-v2

by zackscriven

ghl_payment_custom_provider_create

Creates a new custom payment provider integration for a location by submitting provider details, logo, payment URL, and query URL.

Instructions

Create new integration API to create a new association for an app and location Endpoint: POST /payments/custom-provider/provider (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/custom-provider.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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_payment_custom_provider_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description adds beyond that: the exact endpoint/version header and the required location token plus write scope, which tells the agent what credentials a successful call needs.

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?

It is short and front-loads the purpose, but the content reads like stitched-together OpenAPI metadata: the duplicate title line, a vague second line, an endpoint line, and a spec-source citation ('source: v3/payments-v3.json') that carries no decision value for the agent.

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?

Auth, scope, and endpoint are present and the six-field request body is fully documented with examples, which covers most of what a create call needs. Missing are the response shape (no output schema) and any note on duplicate/integration registration behavior or side effects, which matter for a non-idempotent create.

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 description coverage is 100% with examples for every body field (name, imageUrl, queryUrl, description, paymentsUrl, supportsSubscriptionSchedule) and locationId, so the schema does the semantic work. The description adds nothing about the parameters, including the nested body object, so baseline 3 applies.

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 pairs the verb 'create' with a concrete resource ('a new association for an app and location') and names the exact endpoint, so an agent knows this provisions a custom payment provider integration for a location. It stops short of distinguishing this from the adjacent ghl_payment_custom_provider_create_config sibling, which sounds near-identical.

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 states the hard prerequisites ('Requires a Sub-Account (location) token') and the OAuth scope needed, which is real gating information. However, there is no guidance on when to prefer this tool over create_config, update_capabilities, or integration_provider_create, so the agent must infer selection from the name alone.

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