Skip to main content
Glama
Sign In
GHL MCP Server

GHL MCP Server

by northrosetech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Payment Orders

ghl_list_orders
Read-onlyIdempotent

Retrieve payment orders for a location. Fetch paginated transaction records to view and manage payment history.

Instructions

Get payment orders for a location.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the location scoping but does not disclose pagination behavior, default limits, or whether locationId is required, which would be useful given openWorldHint.

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 description is a single, concise sentence that front-loads the core action. It is efficient, though slightly more detail would improve usefulness without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and sparse description, the tool lacks context about return values, pagination, and how it differs from allied tools. The annotations mitigate safety concerns but do not fill the information gap about expected behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for parameters. The description only hints at locationId through 'for a location' and does not clarify pagination parameters (limit/offset) or requiredness. It fails to compensate for the schema's lack of descriptive coverage.

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?

The description clearly states the tool retrieves payment orders for a location, with a specific resource and scope. It is distinct from the singular ghl_get_order, though it does not explicitly mention alternatives or contrast with similar list tools.

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?

No usage guidance is provided. There is no mention of when to use this tool versus alternatives like ghl_list_transactions or ghl_get_order, nor any prerequisites or exclusions.

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