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

ghl-mcp-server-v2

by zackscriven

ghl_proposal_list_templates

Read-onlyIdempotent

List document and contract templates for a specific location, with optional filters and pagination to page through proposal, estimate, or content library results.

Instructions

List templates List document contract templates for a location Endpoint: GET /proposals/templates (Version header: v3; source: v3/proposals-v3.json) Requires an Agency or Sub-Account token. Pagination params: limit, skip — 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": {
      "locationId": "<locationId>"
    },
    "name": "ghl_proposal_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTemplate Name
skipNoSkip
typeNoComma-separated template types. Valid values: proposal, estimate, contentLibrary
limitNoLimit
dateToNoDate to (ISO 8601)
userIdNoUser Id, required when isPublicDocument is true
dateFromNoDate start from (ISO 8601)
locationIdYesLocation Id
isPublicDocumentNoIf the docForm is a DocForm

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 useful context beyond that: the auth scope (Agency or Sub-Account token), the concrete endpoint, and the pagination contract that implies paged result sets.

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 with purpose, then endpoint, auth, and pagination in compact lines. The one flaw is a slightly redundant title/verb pair ('List templates' followed by the fuller 'List document contract templates'), but nothing is wasted otherwise.

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?

For a read-only listing tool with full schema coverage and no output schema, the description is adequate: endpoint, auth, and paging are all present. It still lacks the sibling disambiguation and any hint about result contents that would make it complete for a nine-parameter list tool.

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 all nine parameters are already documented in structured form. The description only adds usage semantics for limit/skip ('pass them to page through full result sets') and says nothing about type, userId, or isPublicDocument, so it stays at baseline.

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 document contract templates for a location'), which is unambiguous on its own. It doesn't explicitly contrast with closely related siblings like ghl_proposal_list_documents or ghl_estimate_template_list, so an agent must infer the distinction.

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?

It gives useful invocation context—endpoint, API version, required Agency/Sub-Account token, and pagination via limit/skip. However, it never says when to reach for this tool versus ghl_proposal_list_documents or ghl_estimate_template_list, leaving the sibling choice to inference.

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