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

ghl-mcp-server-v2

by zackscriven

ghl_payment_order_create_fulfillment

Create an order fulfillment by submitting fulfilled items and tracking details for a payment order, with optional customer notification.

Instructions

Create order fulfillment The "Order Fulfillment" API facilitates the process of fulfilling an order. Endpoint: POST /payments/orders/{orderId}/fulfillments (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/orders.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": {
      "orderId": "<orderId>",
      "body": "<body>"
    },
    "name": "ghl_payment_order_create_fulfillment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
orderIdYesID of the order that needs to be returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / items / items / title
      Added value: +"FulfillmentItems"
    • addedInput schema / properties / body / properties / trackings / items / title
      Added value: +"FulfillmentTracking"
    • addedInput schema / properties / body / title
      Added value: +"CreateFulfillmentDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so the safety profile is covered structurally. The description adds real value beyond them by disclosing the required Sub-Account token and OAuth scope, plus the underlying endpoint. However, it never explains the practical consequence of idempotentHint=false (duplicate fulfillments possible), nor what happens to order status or when notifyCustomer fires, which would matter for a non-idempotent mutation.

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 verb+resource headline is front-loaded before the boilerplate, which is the right ordering. The middle sentence ('facilitates the process of fulfilling an order') is filler that could be cut, but the endpoint, version header, and scope lines are dense and useful.

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 and a nested request body, an agent still lacks key context: what the response returns, whether the order must be in a specific paid state, and how line items must correspond to the original order. Auth, scope, and endpoint are covered, which keeps it at minimum-viable rather than inadequate.

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%, including nested items, trackings, and notifyCustomer fields, so the schema carries the parameter burden. The description adds nothing about the relationship between items/priceId/qty or the orderId source, so the baseline 3 applies.

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 and resource ('Create order fulfillment') that clearly separates it from the sibling list tool ghl_payment_order_list_fulfillments. The endpoint line (POST /payments/orders/{orderId}/fulfillments) reinforces exactly what object is being created. It stops short of explaining what a 'fulfillment' actually does to the order beyond the generic 'fulfilling an order' phrasing.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative even though ghl_payment_order_list_fulfillments exists. The 'facilitates the process of fulfilling an order' sentence is a restatement rather than guidance. The only actionable context is the prerequisite (Sub-Account token, payments/orders.write scope), which is auth, not usage selection.

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