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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_template_update_late_fees_configuration

Update an invoice template's late fees configuration by template ID to set enablement, fee type, amount, grace period, frequency, and maximum fees.

Instructions

Update template late fees configuration API to update template late fees configuration by template id Endpoint: PATCH /invoices/template/{templateId}/late-fees-configuration (Version header: v3; source: v3/invoices-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": {
      "templateId": "<templateId>",
      "body": "<body>"
    },
    "name": "ghl_invoice_template_update_late_fees_configuration"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / lateFeesConfiguration / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "enable": {
      -        "description": "Enable late fees",
      -        "example": true,
      -        "type": "boolean"
      -      },
      -      "frequency": {
      -        "allOf": [
      -          {
      -            "properties": {
      -              "interval": {
      -                "description": "Late fees interval",
      -                "enum": [
      -                  "minute",
      -                  "hour",
      -                  "day",
      -                  "week",
      -                  "month",
      -                  "one_time"
      -                ],
      -                "example": "day",
      -                "type": "string"
      -              },
      -              "intervalCount": {
      -                "description": "Late fees interval count",
      -                "example": 10,
      -                "type": "number"
      -              }
      -            },
      -            "required": [
      -              "intervalCount",
      -              "interval"
      -            ],
      -            "type": "object"
      -          }
      -        ],
      -        "description": "Late Fees Frequency"
      -      },
      -      "grace": {
      -        "allOf": [
      -          {
      -            "properties": {
      -              "interval": {
      -                "description": "Late fees grace interval",
      -                "enum": [
      -                  "day"
      -                ],
      -                "example": "day",
      -                "type": "string"
      -              },
      -              "intervalCount": {
      -                "description": "Late fees grace interval count",
      -                "example": 10,
      -                "type": "number"
      -              }
      -            },
      -            "required": [
      -              "intervalCount",
      -              "interval"
      -            ],
      -            "type": "object"
      -          }
      -        ],
      -        "description": "Late Fees Grace"
      -      },
      -      "maxLateFees": {
      -        "allOf": [
      -          {
      -            "properties": {
      -              "type": {
      -                "enum": [
      -                  "fixed"
      -                ],
      -                "example": "fixed",
      -                "type": "string"
      -              },
      -              "value": {
      -                "description": "Max late fees to pay",
      -                "example": "10",
      -                "type": "number"
      -              }
      -            },
      -            "required": [
      -              "type",
      -              "value"
      -            ],
      -            "type": "object"
      -          }
      -        ],
      -        "description": "Max late fees payable"
      -      },
      -      "type": {
      -        "description": "Late Fees Type",
      -        "enum": [
      -          "fixed",
      -          "percentage"
      -        ],
      -        "example": "fixed",
      -        "type": "string"
      -      },
      -      "value": {
      -        "description": "Late Fees Value",
      -        "example": 10,
      -        "type": "number"
      -      }
      -    },
      -    "required": [
      -      "enable",
      -      "value",
      -      "type",
      -      "frequency"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "enable": {
      +        "description": "Enable late fees",
      +        "example": true,
      +        "type": "boolean"
      +      },
      +      "frequency": {
      +        "allOf": [
      +          {
      +            "properties": {
      +              "interval": {
      +                "description": "Late fees interval",
      +                "enum": [
      +                  "minute",
      +                  "hour",
      +                  "day",
      +                  "week",
      +                  "month",
      +                  "one_time"
      +                ],
      +                "example": "day",
      +                "type": "string"
      +              },
      +              "intervalCount": {
      +                "description": "Late fees interval count",
      +                "example": 10,
      +                "type": "number"
      +              }
      +            },
      +            "required": [
      +              "intervalCount",
      +              "interval"
      +            ],
      +            "title": "LateFeesFrequencyDto",
      +            "type": "object"
      +          }
      +        ],
      +        "description": "Late Fees Frequency"
      +      },
      +      "grace": {
      +        "allOf": [
      +          {
      +            "properties": {
      +              "interval": {
      +                "description": "Late fees grace interval",
      +                "enum": [
      +                  "day"
      +                ],
      +                "example": "day",
      +                "type": "string"
      +              },
      +              "intervalCount": {
      +                "description": "Late fees grace interval count",
      +                "example": 10,
      +                "type": "number"
      +              }
      +            },
      +            "required": [
      +              "intervalCount",
      +              "interval"
      +            ],
      +            "title": "LateFeesGraceDto",
      +            "type": "object"
      +          }
      +        ],
      +        "description": "Late Fees Grace"
      +      },
      +      "maxLateFees": {
      +        "allOf": [
      +          {
      +            "properties": {
      +              "type": {
      +                "enum": [
      +                  "fixed"
      +                ],
      +                "example": "fixed",
      +                "type": "string"
      +              },
      +              "value": {
      +                "description": "Max late fees to pay",
      +                "example": "10",
      +                "type": "number"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "value"
      +            ],
      +            "title": "LateFeesMaxFeesDto",
      +            "type": "object"
      +          }
      +        ],
      +        "description": "Max late fees payable"
      +      },
      +      "type": {
      +        "description": "Late Fees Type",
      +        "enum": [
      +          "fixed",
      +          "percentage"
      +        ],
      +        "example": "fixed",
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "Late Fees Value",
      +        "example": 10,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "enable",
      +      "value",
      +      "type",
      +      "frequency"
      +    ],
      +    "title": "LateFeesConfigurationDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdateInvoiceLateFeesConfigurationDto"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the auth scope (Agency or Sub-Account token) and API version, which is useful. It does not say whether the late fees configuration is replaced wholesale or merged with existing values, nor what happens to omitted sub-fields like grace or maxLateFees.

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?

Two sentences, but the second is a near-verbatim restatement of the first plus spec-file metadata ('source: v3/invoices-v3.json') that an agent gains little from. The useful auth constraint is parked at the end rather than front-loaded.

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?

Annotations, a fully documented nested schema and the auth requirement together cover most of what an agent needs. What is still missing for a mutation tool with a deep nested body is update semantics: whether the configuration is replaced entirely, whether grace and maxLateFees are optional in practice despite being required in the schema, and any response behavior.

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 field (altId, altType, lateFeesConfiguration, type, value, enable, frequency, grace, maxLateFees) is documented inline. The description only echoes 'by template id', adding no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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 ('Update template late fees configuration') plus the exact endpoint, so an agent knows precisely what object is mutated. It does not explicitly distinguish itself from the sibling ghl_invoice_update_late_fees_configuration (invoice-level vs template-level), leaving that differentiation to the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is an auth prerequisite ('Requires an Agency or Sub-Account token'). There is no statement of when to use this versus ghl_invoice_update_late_fees_configuration, no prerequisites about the template existing, and no exclusions.

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