Skip to main content
Glama

project_delay_notification_email

Write a professional email to notify a client about a missed project deadline. Choose from three scenarios: early warning, on deadline, or already late, with a revised date and brief reason.

Instructions

Write a professional email notifying a client that a project deadline will be missed. The hardest email most freelancers avoid sending — but sending it early, clearly, and without over-apologising is exactly what separates pros from amateurs. Three routes: 'early_warning' (you can see the deadline is at risk before it arrives — best time to raise it, gives the client maximum flexibility), 'on_deadline' (it's the due date and it won't be ready — lead with the new date, short explanation), 'already_late' (you've already missed it — own it, new date, no excuses). Required: client_name, project_name, new_deadline (the revised date you're committing to). Optional: reason (brief, factual — not a list of excuses), what_is_complete (how much is done, reassures the client progress is real), route (early_warning/on_deadline/already_late — defaults to on_deadline), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name
project_nameYesName of the project or deliverable (e.g. 'the website redesign', 'the brand guidelines', 'your mobile app')
new_deadlineYesThe revised delivery date you're committing to (e.g. 'Friday 27 June', 'end of next week', 'Monday 30 June')
reasonNoOptional: brief, factual reason for the delay (e.g. 'a technical issue took longer than expected to resolve', 'I underestimated the scope of the revisions'). Keep it one sentence — don't over-explain.
what_is_completeNoOptional: what is already done, to reassure the client progress is real (e.g. 'The structure and copy are finished — I'm finalising the visual polish', '80% of the build is complete')
routeNoOptional: 'early_warning' (flagging a risk before the deadline arrives — best outcome), 'on_deadline' (the day it was due and it's not ready — default), or 'already_late' (you've already missed it — own it cleanly)
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. Describes output as a professional email draft, mentions no side effects, and clarifies it does not count against draft limit. Does not explicitly state it does not send the email, but tone implies generation.

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?

Well-structured with a clear opening, route explanations, and parameter details. Every sentence adds value; minor motivational language could be trimmed but overall efficient.

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 no output schema, the description adequately conveys what the tool returns (an email draft). Minor gap: does not specify output format (plain text, HTML) or if it's a full email with headers. Sufficient for an AI to use.

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%, baseline 3. Description adds significant value by explaining each parameter's purpose and tone (e.g., reason should be brief and factual, route descriptions). Goes beyond simple schema definitions.

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?

Clearly states it writes a professional email for missed deadlines, with three distinct routes. Differentiates from siblings like 'late_delivery_apology' by specifying early_warning, on_deadline, already_late options.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when to send (early, on deadline, already late) but does not explicitly compare to alternative tools or state when not to use this tool. Implied usage but no exclusions.

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