Skip to main content
Glama

payment_reminder_email

Write a professional payment reminder email for overdue or upcoming invoices. Select tone based on days overdue: friendly, firm, or final. Requires client name and amount due.

Instructions

Write a professional payment reminder email for an overdue or upcoming invoice. Calibrated by tone: 'friendly' for a first nudge (1-7 days late), 'firm' for a second reminder (8-21 days late), or 'final' for a late-stage notice that signals escalation. Always polite but clear — avoids passive-aggression while leaving no ambiguity about what is owed and when. Does not count against your monthly draft limit. Required: client_name, amount_due. Optional: invoice_number, due_date, days_overdue (used to auto-select tone if tone not specified), tone ('friendly' | 'firm' | 'final'), payment_method (e.g. 'bank transfer', 'PayPal'), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or company name for the greeting
amount_dueYesThe amount outstanding, including currency symbol (e.g. '$2,400', '£1,800', '€950')
invoice_numberNoInvoice reference number (e.g. 'INV-042'). Omit if you don't use invoice numbers.
due_dateNoThe original payment due date (e.g. 'June 1', '1 June 2026'). Omit if unknown.
days_overdueNoHow many days past the due date the invoice is. Used to auto-select tone if tone is not provided: 0-7 → friendly, 8-21 → firm, 22+ → final.
toneNo'friendly' (gentle first nudge, assumes oversight), 'firm' (clear expectation, no apology), or 'final' (signals escalation if not resolved). Overrides days_overdue if both provided.
payment_methodNoHow you'd like to be paid (e.g. 'bank transfer', 'PayPal', 'Stripe invoice link'). Omit to leave the payment method open.
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 responsibility. It discloses key behaviors: tone calibration, politeness, avoidance of passive-aggression, no impact on draft limits. It also states required vs optional parameters and the auto-selection logic for tone. It does not mention any potential side effects or restrictions beyond the parameters, but overall provides adequate transparency for a safe email generation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at about five sentences, front-loading the core purpose and then logically detailing tone calibration and parameter usage. Every sentence adds value, and there is no redundancy or unnecessary information.

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 the 8 parameters, 2 required, and no output schema, the description covers the main behavior thoroughly: it explains tone selection, parameter roles, and the fact that the tool does not consume draft limits. It lacks explanation of the return value (the generated email text), but since there is no output schema, this is acceptable. The description is sufficiently complete for an agent to use the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the tone auto-selection algorithm based on days_overdue, the override behavior of tone parameter, and the fact that the tool doesn't affect draft limits. This synthesis goes beyond the individual parameter descriptions, justifying a score above baseline.

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's purpose: 'Write a professional payment reminder email for an overdue or upcoming invoice.' It specifies the verb 'write' and the resource 'payment reminder email', and distinguishes from siblings by detailing tone calibration and auto-selection logic, which is unique among related tools.

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

Usage Guidelines4/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 tone based on days overdue (friendly for 1-7 days, firm for 8-21, final for 22+). It also notes that the tool does not count against a monthly draft limit. However, it does not explicitly differentiate from overlapping sibling tools like 'late_payment_reminder' or 'payment_overdue_final_notice_email', missing opportunities to state when not to use this tool.

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