Skip to main content
Glama

HighLevel Agency & Builder MCP

Check phone routing and number pools

ghl_phone_wallet_audit
Read-onlyIdempotent

Inspect connected-account phone numbers, number pools, missing routing, and forwarding loops. Routing risks do not establish charges or savings.

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_phone_wallet_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  2. Changed2 schema fields changed
    • addedInput schema / properties / locationId / description
      Added value: +"Target HighLevel sub-account location ID."
    • removedInput schema / properties / locationId / pattern
      Removed value: -"^[A-Za-z0-9_-]{1,128}$"
  3. Changed2 schema fields changed
    • removedInput schema / properties / locationId / description
      Removed value: -"Target HighLevel sub-account location ID."
    • addedInput schema / properties / locationId / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral caveat that routing risks do not establish charges or savings, but it does not explain permissions, scope behavior, or output characteristics beyond that.

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

Conciseness5/5

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

Two sentences, front-loaded with the inspection scope and followed by a concise output-interpretation caveat. There is no redundant or wasted text.

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?

This is a read-only audit tool with no output schema, so the description should ideally explain what the audit returns or what constitutes a finding. It names the inspection areas and one important interpretation caveat, but leaves return values and scope behavior implicit.

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 one optional parameter, locationId, with 0% description coverage, and the description never mentions it. It does not clarify whether locationId scopes the connected-account audit or what happens if it is omitted, leaving a meaningful gap.

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 uses a specific verb ('Inspect') and lists concrete resources: connected-account phone numbers, number pools, missing routing, and forwarding loops. This clearly separates it from siblings like ghl_workflow_ivr_builder or ghl_agency_doctor, though it does not explicitly name an alternative tool.

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?

The description says what the tool inspects but gives no explicit guidance on when to use it versus related tools such as ghl_agency_doctor or ghl_workflow_ivr_builder. The caveat about charges and savings is interpretation guidance, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.