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

ghl-mcp-server-v2

by zackscriven

ghl_proposal_send_document

Sends a proposal document to a client by link or email, using the specified document, location, and sender details.

Instructions

Send document Send document to a client Endpoint: POST /proposals/document/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_document"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / ccRecipients / items / title
      Added value: +"CCRecipientItem"
    • changedInput schema / properties / body / properties / notificationSettings / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "receive": {
      -        "properties": {
      -          "subject": {
      -            "type": "string"
      -          },
      -          "templateId": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "templateId",
      -          "subject"
      -        ],
      -        "type": "object"
      -      },
      -      "sender": {
      -        "properties": {
      -          "fromEmail": {
      -            "type": "string"
      -          },
      -          "fromName": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "fromEmail",
      -          "fromName"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "receive",
      -      "sender"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "receive": {
      +        "properties": {
      +          "subject": {
      +            "type": "string"
      +          },
      +          "templateId": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "templateId",
      +          "subject"
      +        ],
      +        "title": "NotificationSendSettingDto",
      +        "type": "object"
      +      },
      +      "sender": {
      +        "properties": {
      +          "fromEmail": {
      +            "type": "string"
      +          },
      +          "fromName": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "fromEmail",
      +          "fromName"
      +        ],
      +        "title": "NotificationSenderSettingDto",
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "receive",
      +      "sender"
      +    ],
      +    "title": "NotificationSettingsDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"SendDocumentDto"
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the bar is lower. The description adds the endpoint path, API version, and token scope requirement, but does not disclose real behavioral traits: that sending dispatches an external communication (email or link), that it is non-idempotent and may re-send, or what side effects occur on the recipient.

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 the endpoint/token info is front-loaded, but the first two lines are near-duplicates ('Send document' / 'Send document to a client'), wasting a sentence on restatement of the name.

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?

There is no output schema, and the description does not say what a successful send returns or how failures (invalid documentId, missing token scope) manifest. For a mutation with a nested body, the description is barely adequate; the schema covers the payload, but the outcome of the call is left opaque.

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 DTO properties are documented in-schema, so the baseline is 3. The description contributes nothing about the body fields, such as which 'medium' is used by default or when notificationSettings must be populated.

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 ('Send document to a client') so the action is unambiguous. However, siblings ghl_proposal_send_template and ghl_proposal_list_documents exist and the description never distinguishes sending a document from sending a template, leaving the agent to 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?

Use is implied (send a proposal document to a client) and a prerequisite is given ('Requires an Agency or Sub-Account token'), which is useful. But there is no guidance on when to choose this over ghl_proposal_send_template, nor any note on prerequisites like an existing documentId.

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