Skip to main content
Glama

invoice_cover_email

Stop sending blank invoice emails. Generate a cover email that frames the invoice with amount, due date, and clear next steps.

Instructions

Write the short professional email that accompanies a sent invoice. Most freelancers attach invoices to a blank or one-line email — this tool generates the cover email that frames the invoice, states the amount and due date, and gives the client a clear next step. Under 80 words. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
amountYesThe invoice total (e.g. '$2,500', '€1,800', '£950')
invoice_numberNoOptional: invoice reference number (e.g. 'INV-0042'). Included in the subject line if provided.
project_nameNoOptional: the project or work this invoice covers (e.g. 'the website redesign', 'May retainer', 'copywriting — Phase 1')
due_dateNoOptional: when payment is due (e.g. 'June 26', 'within 14 days', 'on receipt'). Defaults to a generic 'per our agreed terms' line.
payment_linkNoOptional: a direct payment URL (e.g. a Stripe link, PayPal.me). Adds a one-click CTA to the email.
payment_methodNoOptional: how you'd like to be paid if no payment link (e.g. 'bank transfer — details on the invoice', 'via Stripe')
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses key behaviors: generates an email under 80 words, does not count against draft limit. Does not mention destructive actions, which is appropriate for a 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?

Two concise sentences that front-load the purpose and immediately add valuable constraints. Every word earns its place.

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, the description adequately explains what the tool returns (the cover email) and its key elements (amount, due date, next step, under 80 words). Enough for an agent to understand the output without additional documentation.

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 coverage is 100% with clear descriptions for each parameter. The description adds no new parameter-level meaning beyond the schema, but it does contextualize that the email will include amount and due date (both parameters). Baseline 3 is appropriate.

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?

Description clearly states the tool writes a short professional cover email for an invoice, distinguishing it from sending a blank email. It specifies the content (amount, due date, next step) and constraints (under 80 words). Among many email siblings, this one is uniquely for invoice cover emails.

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 implies when to use (when sending an invoice and needing a professional cover email) and mentions a pragmatic note about not counting against monthly draft limit. However, it lacks explicit when-not-to-use or alternative tools.

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