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

ghl-mcp-server-v2

by zackscriven

ghl_payment_transaction_get

Read-onlyIdempotent

Retrieve details for a single payment transaction by its unique ID and location context to inspect transaction data and status.

Instructions

Get Transaction by ID The "Get Transaction by ID" API allows to retrieve information for a specific transaction using its unique identifier. Use this endpoint to fetch details for a single transaction based on the provided transaction ID. Endpoint: GET /payments/transactions/{transactionId} (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/transactions.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": {
      "transactionId": "<transactionId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_payment_transaction_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesAltId is the unique identifier e.g: location id.
altTypeYesAltType is the type of identifier.
locationIdNoLocationId is the id of the sub-account.
transactionIdYesID of the transaction that needs to be returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful operational context beyond annotations: it requires a Sub-Account (location) token, needs the payments/transactions.readonly OAuth scope, and specifies the v3 version header.

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 sentence, followed by compact operational metadata (endpoint, version header, auth, scope). The opening line redundantly repeats the title and the first two sentences say nearly the same thing, a small amount of waste.

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?

For a read-by-ID tool with full schema coverage and annotations covering the safety profile, the definition supplies what is missing: auth token type, OAuth scope, and endpoint/version. It does not describe the returned transaction shape, but with no output schema that is a minor gap rather than a blocking one.

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%, so all four parameters (transactionId, altId, altType, locationId) are already documented in the schema. The description adds no additional semantics about how altId/altType relate to the required scoping or how locationId interacts with them, so 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+resource: retrieve a single transaction by its unique identifier, with the concrete endpoint GET /payments/transactions/{transactionId}. It is clearly distinguishable from the list-style sibling (ghl_payment_transaction_list) by the singular 'by ID' framing, though it never names that sibling explicitly.

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?

Says to use this endpoint to fetch details for a single transaction when you have a transaction ID, which implies the when-to-use condition. However, it gives no explicit exclusions or routing advice (e.g., 'use transaction_list to search by date/contact'), leaving the agent to infer alternatives.

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