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

ghl-mcp-server-v2

by zackscriven

ghl_estimate_template_list

Read-onlyIdempotent

Lists estimate templates or retrieves a specific template by ID, with search and pagination, so you can browse and select invoice estimate templates for a location.

Instructions

List Estimate Templates Get a list of estimate templates or a specific template by ID Endpoint: GET /invoices/estimate/template (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/estimate.readonly Pagination params: limit, offset — pass them to page through full result sets.

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>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "ghl_estimate_template_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
limitYesLimit the number of items to return
offsetYesNumber of items to skip
searchNoTo search for an estimate template by id / name
altTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds useful context: the underlying endpoint, version header, required token type, OAuth scope, and pagination behavior. The only blemish is advertising get-by-ID without an ID parameter, though the search parameter's 'id / name' description partially covers that.

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?

Front-loaded and compact, with each line carrying endpoint, auth, scope, or pagination information. There is minor redundancy in restating 'List Estimate Templates' followed by 'Get a list of estimate templates,' but it is otherwise efficient.

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 read-only list tool with no output schema and five parameters, it covers auth, scope, endpoint, version, and pagination adequately. It leaves the search behavior and return shape implicit and has the minor get-by-ID ambiguity, but an agent has enough to invoke it correctly.

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 80%, so the baseline is 3. The description adds that limit and offset page through full result sets, but does not explain altId, altType, or search; altType's enum has no schema description and the description does not compensate.

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 ('List Estimate Templates') and names the core operation. It is distinguishable from sibling mutation tools such as ghl_estimate_template_create/update/delete, though the phrase 'or a specific template by ID' is slightly misleading because the schema exposes no dedicated ID parameter.

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?

Provides prerequisites (Agency or Sub-Account token, invoices/estimate.readonly scope) and says to use limit/offset to page through results. However, it never says when to choose this over sibling tools or how to retrieve one template specifically; usage is largely implied.

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