Skip to main content
Glama

late_payment_follow_up_email

Generate professional late payment follow-up emails with three tone options (gentle, firm, final notice) based on overdue days. Requires client name, invoice number, amount, and days overdue.

Instructions

Write the email chasing an unpaid invoice — professionally, without damaging the relationship. Three routes: gentle (first nudge — invoice is a few days past due, tone is friendly and assumes an oversight, no pressure), firm (second or third follow-up — invoice is significantly overdue, tone is clear and direct, includes a deadline to respond), final_notice (last step before escalating — state what happens next: work pause, late fee, collections, or legal — be factual, not emotional). Distinct from re_engagement_email (chasing a prospect who went quiet before signing) and contract_renewal_email (renewing an ongoing relationship). Does not count against your monthly draft limit. Required: client_name, invoice_number, amount, days_overdue. Optional: route ('gentle' | 'firm' | 'final_notice' — default gentle based on days_overdue if not specified), due_date (original due date), project_name, next_step (for final_notice — what you'll do if unpaid: e.g. 'pause work on all active projects', 'add a 2% monthly late fee', 'refer to collections'), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
invoice_numberYesInvoice number or reference — e.g. 'INV-042', '#112', 'the November invoice'. Used directly in the email.
amountYesAmount outstanding — include currency symbol. E.g. '$4,200', '£1,850 + VAT', '$750 (50% balance)'.
days_overdueYesHow many days past the due date the invoice is. Used to calibrate tone and select the default route if route is not specified.
routeNogentle (default for 1–7 days): friendly first nudge, assumes an oversight. firm (default for 8–21 days): direct follow-up with a response deadline. final_notice (default for 22+ days): factual final warning stating what happens next.
due_dateNoOptional: the original due date — e.g. 'June 1', '1 June 2026'. Makes the email more specific.
project_nameNoOptional: project name or description — adds context. E.g. 'the Westbrook website build', 'our Q2 retainer'.
next_stepNoOptional (recommended for final_notice): what you'll do if unpaid. E.g. 'pause work on all active projects until the balance is cleared', 'add a 2% monthly late fee from the original due date', 'refer the balance to a collections agency'. Keep it factual — this is a statement of policy, not a threat.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

With no annotations, the description carries the full transparency burden. It discloses that the tool writes an email (non-destructive), does not count against monthly draft limit, and describes the three routes. However, it does not explicitly state whether the tool sends the email or returns the draft text, leaving some ambiguity about behavior.

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 well-structured, starting with purpose, then detailing routes, sibling differentiation, and parameter list. While slightly long, each sentence adds value. Minor improvement could be tighter wording, but overall it's efficient.

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?

Given no output schema, the description adequately covers input parameters, routes, and sibling differentiation. It explains when to use each route and provides examples. However, it lacks a clear statement about the output (email draft text), which would improve completeness for tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value beyond the schema by explaining route defaults, providing examples for amount and invoice_number, and clarifying next_step usage. The extra context for fields like days_overdue and route enhances understanding beyond schema descriptions alone.

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 the tool writes an unpaid invoice email, specifies three routes (gentle, firm, final_notice), and explicitly distinguishes from siblings re_engagement_email and contract_renewal_email. The verb 'Write' combined with the resource and context makes the purpose unambiguous.

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?

The description provides explicit guidance on when to use each route based on days_overdue (1-7 gentle, 8-21 firm, 22+ final_notice) and mentions default selection. It also names specific sibling alternatives (re_engagement_email, contract_renewal_email) to avoid confusion.

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