Skip to main content
Glama

late_payment_escalation_email

Write a professional email to escalate an unpaid invoice to a senior contact, legal, or collection agency after a final reminder is ignored.

Instructions

Write a professional email escalating an unpaid invoice to a senior contact, the client's finance team, or as a pre-legal notice. Use this after a final payment reminder has gone unanswered — it signals that the matter is now being formally escalated. Calibrated by route: 'manager' addresses the client's manager or director by name; 'legal' is a pre-action letter signalling that formal recovery steps will follow; 'agency' notifies the client that the debt is being passed to a collection or credit-control agency. Tone is firm, factual, and free of emotion — no threats beyond the escalation itself. Distinct from payment_reminder_email (which is sent to the original contact before escalation). Does not count against your monthly draft limit. Required: client_name, amount_due. Optional: invoice_number, due_date, days_overdue, escalation_route ('manager' | 'legal' | 'agency' — defaults to 'legal'), senior_contact_name (first name of the escalation target — omit if unknown), senior_contact_role (e.g. 'Finance Director', 'Head of Operations'), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesName of the client or company the original invoice was issued to
amount_dueYesThe outstanding amount, including currency symbol (e.g. '$2,400', '£1,800')
invoice_numberNoInvoice reference number (e.g. 'INV-042'). Omit if you don't use invoice numbers.
due_dateNoThe original payment due date (e.g. 'May 15', '15 May 2026'). Omit if unknown.
days_overdueNoHow many days past the due date the invoice currently is.
escalation_routeNo'manager' (addressed to a named senior contact at the client company), 'legal' (pre-action letter to the original contact signalling formal recovery), or 'agency' (notifying the client that the debt is being passed to a collection agency). Defaults to 'legal'.
senior_contact_nameNoFirst name of the escalation target — required if escalation_route is 'manager'. Omit for 'legal' or 'agency' routes.
senior_contact_roleNoRole or title of the escalation target (e.g. 'Finance Director', 'Head of Operations'). Used in the 'manager' route to add context.
your_nameNoYour name for the sign-off
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses tone (firm, factual, no threats), calibration by route, and the note about draft limits. It also lists required and optional parameters, providing comprehensive behavioral context.

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?

The description is a single paragraph but well-structured with front-loaded purpose and usage. Every sentence earns its place, though it could be broken into smaller paragraphs for readability.

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?

The description covers all parameters and usage context well, but lacks any mention of what the tool returns (e.g., email body or confirmation). Given the complexity of 9 parameters, this is a gap.

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%, so baseline is 3. The description adds some value by explaining the escalation_route parameter further (defaults to 'legal') and providing usage context for senior_contact_name, but it largely restates schema information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it writes a professional email for escalating unpaid invoices. It specifies the resource (unpaid invoice) and the verb (escalating), and distinguishes from the sibling 'payment_reminder_email' by noting it is used after that reminder has gone unanswered.

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

Usage Guidelines5/5

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

Explicitly states when to use: after a final payment reminder has gone unanswered. It also details three routes (manager, legal, agency) and their specific use cases, and notes that it does not count against the monthly draft limit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jabbawocky/proposalcraft'

If you have feedback or need assistance with the MCP directory API, please join our Discord server