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

ghl-mcp-server-v2

by zackscriven

ghl_estimate_convert_to_invoice

Converts an existing estimate into a new invoice so approved work can be billed without re-entering line items.

Instructions

Creates a new invoice from an accepted/existing estimate. Create Invoice from Estimate Create a new invoice from an existing estimate Endpoint: POST /invoices/estimate/{estimateId}/invoice (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/estimate.write

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": {
      "estimateId": "<estimateId>",
      "body": "<body>"
    },
    "name": "ghl_estimate_convert_to_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
estimateIdYesEstimate Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreateInvoiceFromEstimateDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Adds real value beyond the annotations: token type required (Agency or Sub-Account), OAuth scope (invoices/estimate.write), and the exact endpoint/API version. However, it never says what happens to the source estimate after conversion, whether re-converting an already-invoiced estimate errors out, or that this is a non-idempotent (per annotations) mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is repeated three times in near-identical form ("Creates a new invoice from an accepted/existing estimate", "Create Invoice from Estimate", "Create a new invoice from an existing estimate"), which is pure redundancy. The genuinely useful metadata (endpoint, auth, scope) is buried after the repetition.

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 requirements, scope, and endpoint are covered, which is more than most siblings offer. With no output schema and a nested body, the description should still tell the agent what conversion returns (e.g., the new invoice identifier) and what state the estimate is left in; neither is present.

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% and the nested CreateInvoiceFromEstimateDto fields (altId, altType, version, markAsInvoiced) each carry their own description, so the baseline is 3. The tool description itself adds nothing about parameters, and the ambiguous interaction between 'accepted/existing' in the prose and the required markAsInvoiced flag is not clarified.

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?

Specific verb and resource (creates an invoice) plus the qualifying source object (from an accepted/existing estimate), which implicitly separates it from the sibling ghl_invoice_create. It never names that sibling or any other alternative, so differentiation is left to inference, but the purpose itself is unambiguous.

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?

"accepted/existing estimate" hints at a precondition, but there is no explicit when-to-use / when-not-to-use guidance, no statement about what to do if the estimate is in draft or already invoiced, and no pointer to ghl_invoice_create for creating an invoice from scratch.

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