Skip to main content
Glama

HighLevel Agency & Builder MCP

Show the connected account

ghl_agency_contexts
Read-onlyIdempotent

Show the sub-account selected during connection. Connect again to choose a different sub-account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Optional HighLevel context name to inspect.",
      -  "enum": [
      -    "moosh-growth",
      -    "marketplace-sandbox"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Optional HighLevel context name to inspect.",
      +  "enum": [
      +    "moosh-growth",
      +    "marketplace-sandbox"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Optional HighLevel context name to inspect.",
      -  "enum": [
      -    "moosh-growth",
      -    "marketplace-sandbox"
      -  ],
      -  "type": "string"
      -}
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavior that the value is fixed at connection time and only changes by reconnecting, but says nothing about what is returned (account ID, name, metadata).

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 short sentences, front-loaded with the core behavior and followed by the one actionable caveat. No redundant restatement of the title or name.

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 zero-parameter read tool whose annotations fully cover safety, this is nearly complete. The remaining gap is that, with no output schema, the description never says what 'Show' returns, which is the one thing an agent would still want to know.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no inputs are needed.

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 ('Show') and resource ('the sub-account selected during connection'), so an agent knows this returns the currently active account context. It is distinguishable from siblings like ghl_agency_locations and ghl_agency_connection_health, though the plural name 'contexts' is slightly at odds with the singular 'sub-account' described.

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?

Usage is only implied: call this to see which sub-account is active. The second sentence explains how to change the selection ('Connect again') but names no sibling tool or condition for choosing this over ghl_agency_locations or ghl_agency_doctor.

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.