Skip to main content
Glama

HighLevel Agency & Builder MCP

Set the change policy

ghl_agency_tools_enable

Choose read-only access or allow changes after a preview. Every change still requires dryRun=false and the returned preview ID.

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": {
      "policyPreset": "<policyPreset>"
    },
    "name": "ghl_agency_tools_enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyPresetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / policyPreset / description
      Removed value: -"Safe-Writes Policy preset to apply to the current session."
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "policyPreset"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / policyPreset / description
      Added value: +"Safe-Writes Policy preset to apply to the current session."
    • changedInput schema / required
      Previous value: -[
      -  "policyPreset"
      -]New value: +[]
  3. Changed2 schema fields changed
    • removedInput schema / properties / policyPreset / description
      Removed value: -"Safe-Writes Policy preset to apply to the current session."
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "policyPreset"
      +]
  4. Changed3 schema fields changed
    • removedInput schema / properties / pack
      Removed value: -{
      -  "description": "Domain tool pack to activate in the current session.",
      -  "enum": [
      -    "all",
      -    "core",
      -    "onboarding",
      -    "saas",
      -    "ai",
      -    "telephony",
      -    "commerce",
      -    "governance",
      -    "crm",
      -    "billing",
      -    "announcements"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / policyPreset
      Added value: +{
      +  "description": "Safe-Writes Policy preset to apply to the current session.",
      +  "enum": [
      +    "read-only",
      +    "dry-run-first",
      +    "standard"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / tools
      Removed value: -{
      -  "description": "Explicit list of tool names to enable.",
      -  "items": {
      -    "maxLength": 128,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  "maxItems": 64,
      -  "minItems": 1,
      -  "type": "array"
      -}
  5. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful context that changes require dryRun=false and a returned preview ID, which is beyond the annotations. However, it does not disclose whether the policy change is global, persistent, or reversible, nor what the 'standard' preset actually enables.

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 two sentences with little wasted text, and it front-loads the access-mode choice. The second sentence about dryRun=false and preview IDs is relevant but slightly tangential to setting the policy itself.

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?

For a one-parameter policy-setting tool with no output schema, the description leaves critical gaps: it does not define the three preset values, does not state the scope of the policy, and does not clarify what behavior changes when the policy is applied. An agent would need to guess the meaning of 'standard' and the effect of the call.

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?

Schema description coverage is 0% for the single required enum parameter. The description maps 'read-only' and 'allow changes after a preview' to two possible modes, but it never explains what the 'standard' enum value means and does not explicitly map its wording to the exact enum literals. The parameter semantics remain incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool chooses between read-only access and allowing changes after a preview, which gives a rough sense of the action. However, it never explicitly states that it sets an agency-wide policy preset, and the tool name 'ghl_agency_tools_enable' does not clearly match the title 'Set the change policy' or the description's policy-setting purpose. It also does not distinguish this tool from any sibling.

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 implies a choice between access modes but gives no explicit guidance on when to use this tool, when not to use it, or which alternative sibling tool to use instead. It also does not explain how to choose among the three enum presets (read-only, dry-run-first, standard).

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.