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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_plan_deprecated

Read-onlyIdempotent

Fetch a specific SaaS plan by plan ID and company ID using an agency-level token; use this legacy fallback only when the current plan endpoint is unavailable.

Instructions

DEPRECATED per spec — superseded by GET /saas/saas-plan/{planId}. REQUIRES AN AGENCY-LEVEL (Company) TOKEN. [DEPRECATED per official docs — prefer the documented replacement if one exists.] [LEGACY FALLBACK — this endpoint is no longer in the live v3 docs (checked 2026-10-28) but is still served under the legacy Version header. Expect removal; prefer a current equivalent.] Get SaaS Plan Fetch a specific SaaS plan by plan ID Endpoint: GET /saas-api/public-api/saas-plan/{planId} (Version header: 2021-04-15; source: saas-api.json) Requires an Agency (company-level) token.

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": {
      "planId": "<planId>",
      "companyId": "<companyId>"
    },
    "name": "ghl_saas_get_plan_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYesPlan ID to get SaaS plan details for
companyIdYesCompany ID to filter SaaS plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/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 genuinely new context — agency/company-level token requirement, the 2021-04-15 Version header, and removal risk. The only gap is the repeated deprecation notices, which don't add new behavior information after the first.

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

Conciseness2/5

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

Front-loaded with the deprecation warning, which is good, but the same deprecation fact is restated three separate times (spec line, official-docs bracket, and legacy-fallback bracket), padding the definition considerably. The useful content is roughly two lines that have been inflated into six.

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 two-parameter read tool with no output schema, the description supplies auth scope, endpoint, version header, and lifecycle status — everything needed to call it correctly. Only the successor tool's identity is missing.

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 description coverage is 100%, so both planId and companyId are already documented in the schema. The description contributes no additional semantics about ID format, sourcing, or whether companyId must match the token's company — baseline 3 applies.

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 and resource ('Fetch a specific SaaS plan by plan ID') plus the exact endpoint, so the operation is unambiguous. It does not name the sibling tool that replaces it (likely ghl_saas_get_plan), leaving that mapping to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the tool as a deprecated fallback ('prefer the documented replacement if one exists', 'LEGACY FALLBACK... Expect removal'), which tells the agent when not to use it. It stops short of naming the concrete replacement tool or the condition under which the legacy endpoint still works beyond the Version header note.

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