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

ghl-mcp-server-v2

by zackscriven

ghl_payment_custom_provider_update_capabilities

Idempotent

Update payment capabilities for a custom-provider marketplace app tied to an OAuth client, including whether it supports subscription schedules. Use a sub-account token to toggle these settings.

Instructions

Custom-provider marketplace app update capabilities Toggle capabilities for the marketplace app tied to the OAuth client Endpoint: PUT /payments/custom-provider/capabilities (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": {
      "body": "<body>"
    },
    "name": "ghl_payment_custom_provider_update_capabilities"
  }
}

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true, so the mutation profile is covered. The description adds value beyond that by disclosing the auth requirements (location token, payments/custom-provider.write scope) and the exact HTTP verb/path/version header. It does not explain whether unlisted capabilities are preserved or reset, which is the remaining behavioral gap for a mutation tool.

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 in the first two lines, then terse metadata (endpoint, version, token, scope). No filler sentences. The metadata block is dense but each line carries operational value; slight redundancy between the title-style first line and the verb line.

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?

With only one (nested) body parameter, full schema coverage and no output schema, the description covers what an agent needs to invoke it: purpose, endpoint, auth token type, and required OAuth scope. The only missing piece is post-call effect (whether unspecified capabilities are left intact), which matters for a capabilities mutation.

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% — companyId, locationId and supportsSubscriptionSchedules all carry inline descriptions including the companyId/locationId mutual-mandatory rule. The description adds no parameter-level meaning on top of that, so the baseline 3 applies. Note the description says 'toggle' while the schema requires an explicit boolean, a nuance the description could have clarified.

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: 'Toggle capabilities for the marketplace app tied to the OAuth client', which clearly distinguishes it from sibling custom-provider tools (create_config, get_config, disconnect_config, delete). The endpoint line reinforces exactly what operation is performed. It does not explicitly name a sibling it is not, so it falls just short of 5.

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 supplies real prerequisites — Sub-Account (location) token required and OAuth scope payments/custom-provider.write — which tells the agent when it is even callable. However, there is no guidance on when to choose this over ghl_payment_custom_provider_create_config or create, nor any when-not-to-use condition. Usage context is implied by the scope, not 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