Skip to main content
Glama

payment_overdue_final_notice_email

Send a final notice email for overdue invoices, stating amount, days overdue, and a deadline before escalating to collection, legal action, or work suspension.

Instructions

Write the formal final notice email when a client has not responded to previous payment reminders and the invoice is significantly overdue. This is the last professional communication before escalating to a collection agency, pausing all work, or seeking legal remedy — so the tone is firm, factual, and unambiguous without being hostile. States the outstanding amount, the number of days overdue, and a clear deadline for payment before you take the next step. Named 'final notice' so the client understands this is the last communication in the sequence. Distinct from late_payment_reminder (earlier, softer reminders) and invoice_dispute_response_email (client disputes the charge — this is non-payment, not dispute). Does not count against your monthly draft limit. Required: client_name, invoice_number, amount, days_overdue. Optional: original_due_date, payment_deadline (days from this email before next step — defaults to 7), next_step (collection_agency | legal_action | work_suspension — defaults to work_suspension), project_name, payment_link, your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
invoice_numberYesInvoice reference number (e.g. 'INV-042', '#2024-07')
amountYesThe outstanding amount as a string (e.g. '$1,200', '£850')
days_overdueYesHow many days past the due date the invoice is (e.g. 30, 45, 60)
original_due_dateNoThe original due date (e.g. 'June 5', '5 June 2026'). Stating it makes the timeline clear and removes ambiguity.
payment_deadlineNoNumber of days from this email the client has to pay before you take the next step. Defaults to 7.
next_stepNoWhat you will do if payment is not received by the deadline. work_suspension (default): pause all work and withhold deliverables. collection_agency: refer the debt to a collection agency. legal_action: pursue through small claims or formal legal channels.
project_nameNoProject name for context (e.g. 'the Brand Refresh project', 'the Q2 content package')
payment_linkNoA direct payment link or portal URL if you have one — makes it frictionless for the client to pay immediately
your_nameNoYour name for the sign-off
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that the tool does not count against monthly draft limits and sets expectations for tone (firm, factual, unambiguous). However, it does not clarify whether the tool actually sends the email or only drafts it, which is a minor gap.

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 logically structured and front-loaded with purpose and usage. It provides necessary information without redundancy, though it could be slightly more concise by trimming some explanatory phrases. Every sentence contributes meaning.

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 10 parameters, no output schema, and moderate complexity, the description covers purpose, usage, parameter details, and sibling differentiation. It lacks explicit mention of return values (e.g., draft text content), but as an email drafting tool, this is partially inferable. Overall, it is quite complete.

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%, so baseline is 3. The description adds value by listing required and optional parameters, specifying defaults (e.g., payment_deadline defaults to 7, next_step defaults to work_suspension), and explaining enum options for next_step. This surpasses basic schema details.

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 formal final notice email for overdue invoices, using a specific verb and resource. It explicitly distinguishes from sibling tools 'late_payment_reminder' and 'invoice_dispute_response_email', providing clear differentiation.

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 specifies when to use (client not responded to previous reminders, significantly overdue) and contrasts with alternatives, including explicit 'when-not-to-use' through sibling differentiation. It also notes this is the last communication before escalation.

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