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

ghl-mcp-server-v2

by zackscriven

ghl_estimate_list

Read-onlyIdempotent

Retrieve a paginated list of estimates filtered by status, date range, contact, or search text to review and manage billing records.

Instructions

List Estimates Get a paginated list of estimates Endpoint: GET /invoices/estimate/list (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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
endAtNoendAt in YYYY-MM-DD format
limitYesLimit the number of items to return
offsetYesNumber of items to skip
searchNosearch text for estimates name
statusNoestimate status
altTypeYes
startAtNostartAt in YYYY-MM-DD format
contactIdNoContact ID for the estimate

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 readOnly/idempotent/non-destructive, and the description adds real operational context beyond them: the required token type (Agency or Sub-Account), the OAuth scope invoices/estimate.readonly, and the paging behavior. What it omits is the response item shape and default page size.

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 auth, then pagination, each on its own line. The endpoint/version/source line is mostly metadata noise for an agent, but the rest is tight and scannable.

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?

With no output schema, auth requirements and paging are the critical pieces and both are present. Return value structure is left to the schema's absence, and the filter parameters are only covered by schema descriptions, so it is solid but not complete.

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 89%, so the schema already documents altId, status, search, startAt/endAt, contactId. The description adds only that limit and offset are pagination parameters used to walk full result sets, which is a small increment over the schema's own wording.

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 paginated list of estimates' plus the exact endpoint. It does not distinguish itself from siblings like ghl_estimate_create, ghl_estimate_update, or ghl_estimate_template_list, so differentiation is left to the reader.

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?

Implies usage as the read/list counterpart to the estimate siblings and supplies the paging instruction for limit/offset, but gives no explicit when-to-use guidance, no mention of which filters to combine, and no exclusions relative to other listing tools.

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