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

ghl-mcp-server-v2

by zackscriven

ghl_invoice_update_late_fees_configuration

Updates an invoice's late-fees configuration by invoice ID, including enablement, value, type, frequency, grace period, and maximum fees.

Instructions

Update invoice late fees configuration API to update invoice late fees configuration by invoice id Endpoint: PATCH /invoices/{invoiceId}/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": {
      "invoiceId": "<invoiceId>",
      "body": "<body>"
    },
    "name": "ghl_invoice_update_late_fees_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
invoiceIdYesInvoice 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the write profile is known. The description adds genuinely useful context in the required token scope and the PATCH endpoint/version. It does not disclose that lateFeesConfiguration appears to be a full replacement of the configuration, or what the response contains, so mutation semantics remain partly opaque.

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?

Purpose is front-loaded in the first sentence and the rest is supporting operational detail. The 'source: v3/invoices-v3.json' provenance fragment is spec noise that does not earn its place, keeping this from a 5.

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?

No output schema exists, so the description needn't explain returns, and the input schema is rich and fully annotated. Auth scope, endpoint, and version header are all covered; the only meaningful gap is the absence of any mention of the template-level sibling for disambiguation.

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?

With 100% schema description coverage and fully documented nested objects (type, value, enable, frequency, grace, maxLateFees), the schema carries the parameter burden and the baseline of 3 applies. The description adds only the invoiceId mapping via 'by invoice id' and nothing about the body's all-or-nothing required set beyond what the schema states.

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 invoice late fees configuration') plus the keying mechanism ('by invoice id'), and the endpoint path confirms the resource. This implicitly distinguishes it from the sibling ghl_invoice_template_update_late_fees_configuration, but never names that sibling explicitly, so differentiation relies on the agent reading both names.

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 auth note ('Requires an Agency or Sub-Account token') gives a precondition, and 'by invoice id' implies this is per-invoice rather than per-template. However, there is no explicit when-to-use/when-not guidance and no reference to the near-identical template-level sibling, which is the most likely source of wrong selection.

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