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

ghl-mcp-server-v2

by zackscriven

ghl_payment_custom_provider_delete

DestructiveIdempotent

Permanently removes a custom payment provider integration for a location, not just its configuration; dependent payment flows will fail afterward.

Instructions

Permanently removes the custom payment provider integration itself (not just its config). Any in-flight or future payment flows depending on it will fail. Deleting an existing integration API to delete an association for an app and location Endpoint: DELETE /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>"
    },
    "name": "ghl_payment_custom_provider_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation profile is covered structurally. The description adds real value on top: the blast radius ('in-flight or future payment flows depending on it will fail') and the auth requirements (Sub-Account/location token, payments/custom-provider.write scope), which annotations cannot express.

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

Conciseness4/5

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

The highest-value sentence (permanent removal + downstream failure) is front-loaded. The middle lines restate the title and add a confusing 'delete an association for an app and location' phrasing that doesn't match the provider-deletion framing, which is minor noise.

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?

No output schema exists, but the description gives endpoint, version, source, auth token type and OAuth scope – enough for correct invocation of a single-parameter destructive tool. What happens on success (empty response? cascade effects on existing orders) is left unstated.

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?

Only one parameter with 100% schema description coverage, so the schema already documents locationId. The description adds nothing about its format or constraints, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource: permanently removes the custom payment provider integration itself, explicitly excluding just its config. That parenthetical cleanly separates it from sibling tools like ghl_payment_custom_provider_disconnect_config and ghl_payment_custom_provider_create_config.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the delete-the-integration case versus the config-only case, and warns that dependent payment flows will fail. It stops short of naming the alternative tool (disconnect_config) explicitly, so the agent must infer the sibling by name.

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