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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_plan

Read-onlyIdempotent

Retrieves a SaaS plan by plan ID and company ID with an agency-level token, enabling you to look up plan details for a specific company.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Get SaaS Plan Fetch a specific SaaS plan by plan ID Endpoint: GET /saas/saas-plan/{planId} (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": {
      "planId": "<planId>",
      "companyId": "<companyId>"
    },
    "name": "ghl_saas_get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes
companyIdYes

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it requires an Agency (company-level) token, specifies the OAuth scope saas/company.read, and names the exact endpoint/version. This helps the agent understand auth prerequisites before calling.

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 key auth requirement is front-loaded, which is good. However, the agency-token requirement is stated twice ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN' and 'Requires an Agency (company-level) token'), creating redundancy. The endpoint and scope lines are useful but the duplicate sentence does not earn its place.

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 need not explain return values. It covers auth scope, endpoint, and version, which is helpful for a read operation. However, it leaves the required companyId parameter unexplained and does not clarify the response shape or error behavior, so it is only adequately complete for a two-required-parameter tool.

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 compensate. It mentions fetching by 'plan ID' but does not explain what planId represents beyond its name, and it never mentions companyId at all despite that being a required parameter. The description adds marginal parameter meaning.

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 clearly states a specific verb and resource: 'Fetch a specific SaaS plan by plan ID,' along with the exact endpoint. It distinguishes a single-plan fetch from broader plan operations only implicitly (e.g., 'specific'), and does not explicitly name siblings such as ghl_saas_get_agency_plans or ghl_saas_get_plan_deprecated.

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 gives useful context about agency-level token requirements and OAuth scopes, which imply when this tool is usable. However, it does not explicitly say when to use this versus ghl_saas_get_agency_plans or the deprecated variant, nor does it state exclusions.

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