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

ghl-mcp-server-v2

by zackscriven

ghl_saas_update_location_wallet_balance

Adds or adjusts complimentary wallet credits for a specific location. Use an agency-level token; partial updates are supported via updateMask.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Adds/adjusts complimentary wallet credits for the given location. Update Location Wallet Balance Update the wallet balance or complimentary credit settings for a specific location. Supports partial updates via updateMask field (AIP-134 compliant). Endpoint: POST /saas/companies/{companyId}/locations/{locationId}/wallet-balance/complimentary-credits (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.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": {
      "companyId": "<companyId>",
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_saas_update_location_wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
companyIdYesCompany ID that owns the location
locationIdYesLocation ID to update wallet balance for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"ComplimentaryCreditDTO"
    • addedInput schema / properties / companyId / example
      Added value: +"5DP4iH6HLkQsiKESj6rh"
    • addedInput schema / properties / locationId / example
      Added value: +"AUKAtFVo0lWezBsBQ3FE"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world, so the description earns credit for what it adds: the agency-token requirement, the OAuth scope, the concrete endpoint and version header, and the crucial hint that the value is additive ('credit amount to be added'). It stops short of saying what happens to existing credits or what the response contains after the adjustment, which matters for a financial mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The auth requirement is correctly front-loaded, but the Agency-token requirement is stated twice (

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?

For a write tool with no output schema, the definition covers auth, endpoint and additive semantics but leaves gaps an agent would need: whether the amount is added to or replaces the existing balance, whether agency wallet funds must exist, and what the response reports. Annotations plus full schema coverage carry the remaining weight, so this is adequate but not complete.

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 100%, so companyId, locationId and body are already documented, and the description adds no syntax or constraint detail beyond them. Worse, it advertises a 'updateMask field (AIP-134 compliant)' for partial updates that does not exist anywhere in the schema, which can mislead an agent trying to construct a partial request.

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 gives a specific verb ('Adds/adjusts') and resource ('complimentary wallet credits for the given location'), and the mutation framing clearly separates it from read-only siblings such as ghl_saas_get_location_wallet_balance and ghl_saas_list_location_wallet_transactions. It does not name those siblings explicitly, and the second sentence shifts to vaguer language ('wallet balance or complimentary credit settings'), slightly clouding whether this sets a balance or adds credits.

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?

Prerequisites are stated clearly and twice (Agency/company-level token, saas/company.write scope), which is genuinely useful routing information. However, there is no guidance on when to call this versus inspecting state first with get_location_wallet_balance, and no when-not conditions or warnings about the effect on existing credits.

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