Skip to main content
Glama

late_payment_reminder

Generate overdue-payment reminders for unpaid invoices. Include invoice details, keep tone firm but not hostile, and provide a payment link. Optionally escalate with a second reminder mentioning late fees or paused work.

Instructions

Write a professional overdue-payment reminder when a client has not paid an invoice by the due date. States the invoice details clearly, keeps the tone firm but not hostile, and gives a direct path to pay. A second-reminder variant adds a firmer note about next steps (late fee, pausing work). Distinct from invoice_cover_email (accompanying a fresh invoice) and deposit_request_email (requesting upfront payment). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
invoice_numberNoInvoice reference number (e.g. 'INV-042', '#2024-07')
amountNoThe overdue amount as a string (e.g. '$1,200', '£850')
due_dateNoThe original due date (e.g. 'June 5', '5 June 2026')
days_overdueNoHow many days past the due date the invoice is (e.g. 7, 14, 30)
payment_linkNoA direct payment link or portal URL if you have one
is_second_reminderNoSet to true for a firmer second reminder that mentions next steps (late fee, pausing work) — defaults to false
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 behavioral traits: the tone ('firm but not hostile'), the variant behavior, and importantly that it 'does not count against your monthly draft limit'. This sufficiently conveys the non-destructive, consumption-neutral nature of the 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 three sentences plus a short final note. It is front-loaded with the purpose, efficiently describes the variant, distinguishes from siblings, and adds a behavioral note. No sentence is wasted.

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?

For a content-generation tool with 8 parameters (all described in schema) and no output schema, the description adequately covers the scenario, variant, and a consumption behavior. It lacks explicit mention of the return value (the drafted email), but that is implied. Overall complete given the complexity.

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 the baseline is 3. The description does not add additional meaning beyond what the schema already provides for each parameter. It gives overall context for the tool's output but no parameter-level enrichment.

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 verb 'write', the resource 'overdue-payment reminder', and the condition 'when a client has not paid an invoice by the due date'. It also explicitly distinguishes the tool from two sibling tools: invoice_cover_email and deposit_request_email.

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 context for when to use the tool ('when a client has not paid an invoice by the due date') and describes the second-reminder variant. However, it does not explicitly state when not to use it, nor does it mention other alternatives beyond the two siblings.

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