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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_location_subscription

Read-onlyIdempotent

Fetch subscription details for a specific location from metadata using an agency-level token; requires locationId and companyId.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Get Location Subscription Details Fetch subscription details for a specific location from location metadata Endpoint: GET /saas/get-saas-subscription/{locationId} (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.read

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": {
      "locationId": "<locationId>",
      "companyId": "<companyId>"
    },
    "name": "ghl_saas_get_location_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYes
locationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds non-obvious operational context: agency-token requirement, the v3 version header, the source spec file, and required OAuth scope — all things an agent must know before calling. It stops short of describing error behavior if the location has no subscription.

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 core facts are front-loaded (auth requirement first, then purpose, then endpoint), which is good. But the agency-token requirement is stated twice in near-identical wording, and the source-file citation ('source: v3/saas-api-v3.json') is metadata that does not help an agent decide or call.

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?

There is no output schema, so the description is the only place to learn what a 'subscription detail' contains (plan, status, rebilling config, wallet?), and it says nothing about return shape. Combined with the unexplained companyId parameter, an agent can identify the tool but cannot fully predict the response or the identifier contract.

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%, so the description must carry the burden, but it only implicitly documents locationId through the URL path template. companyId is a required parameter that appears nowhere in the description and has no schema description, leaving the agent to guess its meaning and why it is required alongside an agency token.

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 ('Fetch subscription details for a specific location') and grounds it with the concrete endpoint GET /saas/get-saas-subscription/{locationId}. It is clear what the tool returns at a high level, though it never distinguishes itself from the near-identical sibling ghl_saas_get_location_subscription_deprecated or from ghl_saas_get_plan.

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?

The description strongly gates usage via 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only' and names OAuth scopes saas/company.read, which is genuinely useful selection criteria. However it gives no guidance on when to pick this over the sibling deprecated variant or ghl_saas_get_plan, and no when-not-to-use conditions.

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