Skip to main content
Glama

invoice_correction_email

Generate a professional email to correct a previously sent invoice, with a brief apology, instruction to disregard the original, and clear corrected details.

Instructions

Write the professional email to send a client when you need to correct an invoice you already sent — wrong amount, wrong line item, wrong date, or a missing item. Brief apology (one line — not grovelling), clear instruction to disregard the original, and the corrected details. Gets this right where most freelancers fumble: either they don't send anything (client pays the wrong amount) or they send a confusing email that makes the situation worse. Distinct from invoice_dispute_response_email (the client disputes your invoice — this is when YOU caught the error) and invoice_cover_email (first send of a new invoice). Does not count against your monthly draft limit. Required: client_name, original_invoice_number, corrected_invoice_number, correction_description (e.g. 'the total was listed as $1,200 instead of $1,450 due to a line item error'). Optional: correct_amount, project_name, payment_due_date, payment_link, your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
original_invoice_numberYesThe reference number of the incorrect invoice to disregard (e.g. 'INV-041')
corrected_invoice_numberYesThe reference number of the corrected invoice (e.g. 'INV-041-R', 'INV-042')
correction_descriptionYesWhat was wrong and what it has been corrected to — be specific (e.g. 'the subtotal was listed as $1,200 instead of $1,450 — one line item was missing', 'the due date was listed as June 10 instead of June 20')
correct_amountNoThe correct final amount (e.g. '$1,450', '£2,800'). Including this removes ambiguity about what the client should pay.
project_nameNoProject name for context (e.g. 'the Brand Refresh project')
payment_due_dateNoWhen payment is due on the corrected invoice (e.g. 'June 25', '30 days from today')
payment_linkNoA direct payment link or portal URL for the corrected invoice
your_nameNoYour name for the sign-off
Behavior5/5

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

The description covers behavioral aspects thoroughly: brief apology, instruction to disregard original, corrected details. It also notes it does not count against monthly draft limit and lists required/optional parameters. Since no annotations exist, this is fully comprehensive.

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 informative but somewhat long. It is well-structured: purpose, comparisons, common mistakes, and parameter list. Could be slightly more concise, but no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description covers all necessary context: purpose, usage, behavior, parameters. It explains what the output (email) should contain and provides enough detail for correct invocation.

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 grouping parameters into required and optional, providing examples, and explaining the role of each in the email. However, the schema descriptions are already detailed, so the added value is moderate.

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 a professional email to correct a sent invoice, distinguishing it from sibling tools 'invoice_dispute_response_email' (client disputes) and 'invoice_cover_email' (first send). It uses specific verbs and resources, and the title is clear.

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 explains when to use (when you need to correct an invoice) and when not to use (dispute, first send). It also describes common mistakes, providing clear guidance on context and alternatives.

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