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

ghl-mcp-server-v2

by zackscriven

ghl_payment_custom_provider_get_config

Read-onlyIdempotent

Retrieve an existing custom payment provider configuration for a specific location using its location ID. Use it to inspect payment settings before updates or troubleshooting.

Instructions

Fetch given provider config API for fetching an existing payment config for given location Endpoint: GET /payments/custom-provider/connect (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/custom-provider.readonly

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_get_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation id

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description's added value is auth and API context: the exact endpoint, the v3 version header, the location-token requirement and the payments/custom-provider.readonly OAuth scope. That is genuinely useful context an agent cannot get from the structured fields, short of any note on error behavior for missing configs.

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?

Front-loaded with the purpose, then supporting API metadata in short lines. Mostly every line earns its place, though the source-file reference (v3/payments-v3.json) is internal noise an agent does not need.

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?

There is no output schema, and the description says nothing about the shape of the returned config (e.g. whether it includes provider credentials, capabilities, or connection status), which is the one thing an agent would want to know before calling. Auth and endpoint context are complete, so it is adequate but with a clear return-value gap.

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% and there is a single required locationId with an example, so the schema already carries the semantics. The description's "for given location" only restates it, adding no format or constraint detail beyond the schema.

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?

States a specific verb+resource: fetch an existing payment provider config for a given location, backed by the concrete endpoint GET /payments/custom-provider/connect. It is distinguishable from the sibling mutation tools (create_config, update_capabilities, disconnect_config, delete), though it never names them.

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?

Usage is implied by "fetching an existing" versus the create/update/delete siblings, and the description adds the precondition that a Sub-Account (location) token is required. There is no explicit statement of when to prefer this over the other custom-provider tools or what happens if no config exists.

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