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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_template_get

Read-onlyIdempotent

Retrieve an invoice template by template ID and location/company ID to inspect its details or reuse its structure.

Instructions

Get an template API to get an template by template id Endpoint: GET /invoices/template/{templateId} (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/template.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": {
      "templateId": "<templateId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_invoice_template_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYeslocation Id / company Id based on altType
altTypeYesAlt Type
templateIdYesTemplate Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond that: it names the required token type (Agency or Sub-Account) and the OAuth scope invoices/template.readonly, plus the API version header, which are not derivable from the annotations.

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?

It is short and front-loaded, but the first two lines are redundant ('Get an template' / 'API to get an template by template id') and the endpoint line partly duplicates the schema's path parameter. The auth and scope lines are the real content and are correctly placed after the identity of the call.

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 single-resource fetch with no output schema, the description supplies auth requirements, scope and endpoint, which is enough for an agent to call it correctly; only the shape of the returned template is unspecified, which is acceptable for a GET-by-id.

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% with three documented parameters (templateId, altId, altType, the latter with an enum), so the schema carries parameter meaning. The description only reinforces that templateId is the lookup key and adds nothing about how altId/altType scope the lookup — baseline 3 is appropriate.

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 states a specific verb and resource (retrieve a single invoice template by template id) and pairs it with the concrete endpoint GET /invoices/template/{templateId}, which unambiguously separates it from list/update/delete template siblings. It loses a point for the sloppy opening line ('Get an template') that simply restates the title rather than adding precision.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus ghl_invoice_template_list or the estimate template equivalents; the only implicit cue is 'by template id', which an agent must infer means a single-record fetch. No prerequisites are stated beyond the token requirement.

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