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

ghl-mcp-server-v2

by zackscriven

ghl_payment_order_list_fulfillments

Read-onlyIdempotent

List all fulfillment records for a specific payment order by providing its order ID, location ID, and location type.

Instructions

List fulfillment List all fulfillment history of an order Endpoint: GET /payments/orders/{orderId}/fulfillments (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/orders.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": {
      "altId": "<altId>",
      "altType": "<altType>",
      "orderId": "<orderId>"
    },
    "name": "ghl_payment_order_list_fulfillments"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
orderIdYesID of the order that needs to be returned

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 (readOnly, idempotent, non-destructive), and the description adds non-obvious context: the exact endpoint, the v3 version header, and the required Sub-Account token plus OAuth scope. That auth and versioning detail is genuinely useful for avoiding a failed call. It omits whether results are paginated or capped, which is the main remaining behavioral unknown.

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?

Purpose is front-loaded in the first two lines, and the remaining lines are short factual attributes (endpoint, version, auth, scope). The repeated "List fulfillment" heading is redundant with the title and the source-file path (v3/payments-v3.json) is implementation metadata an agent will never act on, but the bulk of the text earns its place.

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?

With no output schema, the description carries the burden of describing what comes back, and it says nothing about the shape of a fulfillment record, whether the response is an array or wrapped object, or how many items a single call returns. For a read-only list tool the auth and endpoint info is sufficient to invoke it, but not to interpret or page through the result.

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 coverage is 67%: altId and orderId have descriptions, while altType only carries the 'location' enum. The line "Requires a Sub-Account (location) token" usefully explains why altType is constrained to location and what altId represents, but it adds no detail on orderId format or identifier sourcing. This is roughly the baseline for partially documented parameters.

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?

"List all fulfillment history of an order" gives a specific verb (list) and resource (fulfillment history scoped to one order), which separates it from the write sibling ghl_payment_order_create_fulfillment. It stops short of naming that sibling or any other alternative explicitly, so an agent must infer the split from the verb alone.

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 establishes prerequisites (Sub-Account/location token, payments/orders.readonly scope) and that an orderId is the anchor of the query, which implies when it applies. It never states when to prefer this over ghl_payment_order_get or the create-fulfillment sibling, and gives no guidance on pagination or result-size limits for a list endpoint.

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