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

ghl-mcp-server-v2

by zackscriven

ghl_estimate_template_preview

Read-onlyIdempotent

Preview an estimate template for a location or agency using its template ID to verify content before creating estimates.

Instructions

Preview Estimate Template Get a preview of an estimate template Endpoint: GET /invoices/estimate/template/preview (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/estimate.readonly

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": {
      "altId": "<altId>",
      "altType": "<altType>",
      "templateId": "<templateId>"
    },
    "name": "ghl_estimate_template_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
templateIdYesTemplate Id

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description meaningfully adds that an Agency or Sub-Account token is required and lists the OAuth scope (invoices/estimate.readonly) plus the API version header — context not present in annotations. It does not describe the preview's output form.

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 purpose is front-loaded and the endpoint, auth, and scope lines each carry concrete information. Slight redundancy between the title line and the 'Get a preview' sentence, but overall tight and well-ordered.

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?

Auth, scope, and endpoint are documented, which is good for a read-only preview. However, with no output schema, the description never says what a preview actually returns (rendered HTML, URL, object), leaving a real gap for correct invocation/expectation.

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 coverage is 67%, with altId and templateId described and altType constrained by a single-value enum. Baseline 3 applies, but the description adds nothing about parameter meaning and leaves the altId 'Location Id or Agency Id' ambiguity to the schema alone.

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 ('Get a preview of an estimate template') and even names the underlying endpoint GET /invoices/estimate/template/preview. The purpose is unmistakable, though it doesn't explicitly contrast with siblings like ghl_estimate_template_list or ghl_estimate_template_create.

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 — a preview presumably precedes creating or sending an estimate. The description offers no explicit when-to-use, when-not-to-use, or alternative routing, so an agent must infer the place of this tool among the estimate-template siblings.

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