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

ghl-mcp-server-v2

by zackscriven

ghl_proposal_send_template

Send a proposal template to a client by specifying template, user, location, and contact IDs, with optional opportunity linking and document delivery.

Instructions

Send template Send template to a client Endpoint: POST /proposals/templates/send (Version header: v3; source: v3/proposals-v3.json) Requires an Agency or Sub-Account token.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is known. The description adds genuinely useful context: API version header v3 and the Agency/Sub-Account token scope. It still omits the most consequential behavior for a non-idempotent send — whether a message actually goes out to the contact and whether repeat calls duplicate sends.

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?

Four short lines, front-loaded with the action before the endpoint and auth details. The opening 'Send template' duplicates the title verbatim, which is mildly wasteful but the rest is dense and earns its space.

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?

With a single nested body object of six fields, full schema coverage, annotations, and no output schema, the definition covers the mechanics of the call. It falls short on outcome semantics — what the send does to the client and what the response returns — which matters for a side-effecting, non-idempotent operation.

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 every nested property (templateId, userId, locationId, contactId, sendDocument, opportunityId) carries its own description and example, so the schema does the heavy lifting. The prose in the description adds nothing about parameter meaning, which matches the baseline of 3.

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?

Names a specific verb+resource ('Send template to a client') and pins the exact endpoint (POST /proposals/templates/send), so the agent knows this is a proposal-template dispatch action. It does not differentiate itself from close siblings such as ghl_proposal_send_document or ghl_proposal_list_templates, so the agent must infer the split.

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?

The phrase 'to a client' implies proactive sending rather than drafting, and the token requirement ('Agency or Sub-Account') gives a precondition for use. But there is no explicit when-to-use vs. send_document/list_templates guidance and no statement of what happens after the send (email delivery? document record creation?).

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