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

ghl-mcp-server-v2

by zackscriven

ghl_payment_custom_provider_disconnect_config

Disconnects a location's custom payment provider live or test configuration, which stops related payment collection until the provider is reconnected.

Instructions

Disconnects the custom payment provider's live/test config. This can interrupt live payment collection at this location until reconnected. Disconnect existing provider config API to disconnect an existing payment config for given location Endpoint: POST /payments/custom-provider/disconnect (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_disconnect_config"
  }
}

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: +"DeleteCustomProvidersConfigDto"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world mutation, and the description adds important operational context: it can interrupt live payment collection until reconnected and requires a Sub-Account token with the payments/custom-provider.write scope. The warning does not directly contradict destructiveHint=false because disconnecting is presented as a reversible disruption rather than an irreversible delete.

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?

The critical warning is front-loaded, but the description repeats the same idea across 'Disconnects…', 'Disconnect existing provider config,' and 'API to disconnect an existing payment config.' Endpoint and OAuth metadata are useful context, but the duplicated disconnect phrasing makes it less concise than it could be.

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 two-parameter mutation with a fully described schema, the description covers purpose, operational risk, authentication requirements, and endpoint context. It does not explain the response, but no output schema exists and the annotation already covers read-only/idempotency status.

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%, so the schema already explains locationId and the liveMode boolean. The description mentions live/test config and a given location but does not add syntax, format, or selection guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, 'Disconnects,' and a specific resource, 'the custom payment provider's live/test config' at a location. It differentiates itself from sibling provider create/delete/get operations by focusing on disconnecting an existing config rather than deleting the provider.

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 makes the basic use case clear: disconnect an existing payment config for a location. However, it does not explicitly state when to use this instead of sibling tools such as deleting the provider or creating a new config, nor does it list exclusions.

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