Skip to main content
Glama

early_delivery_email

Write a client email announcing early delivery of work, framing it positively and giving a clear next step. Offers full delivery or early preview for feedback.

Instructions

Write the email when your work is ready ahead of the agreed deadline — the email most freelancers mishandle by either sitting on finished work until the deadline (wasted goodwill) or sending with no context (client doesn't know what to do with it). This generates a confident, warm note that announces early delivery, frames it positively, and gives the client a clear next step. Two routes: full_delivery (default — everything is done and ready; confident announcement with handover details and a brief note on what you'd like from them next), early_preview (a first draft or near-complete version is ready before expected — inviting early feedback so you can finalise faster; useful for iterative projects). Distinct from project_completion_email (delivery at the expected time), project_handover_email (operational asset handover with checklist), and milestone_approval_request_email (mid-project sign-off gate). Does not count against your monthly draft limit. Required: client_name, deliverables (what you're sending — e.g. 'the homepage design', 'the three proposal templates', 'the full copy deck'). Optional: project_name, original_deadline (the date they were expecting it — makes the earliness concrete, e.g. 'Friday 27 June', 'end of next week'), feedback_window (how long you can accommodate revisions on your current schedule, e.g. 'the next few days', 'this week' — omit to keep it open), route ('full_delivery' | 'early_preview' — default full_delivery), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient first name
deliverablesYesWhat you're sending early — e.g. 'the homepage design', 'the three proposal templates', 'the full copy deck'
project_nameNoOptional: project name — e.g. 'the Hartley rebrand', 'your Q3 content pack'
original_deadlineNoOptional: when they were expecting the work — e.g. 'Friday 27 June', 'end of next week'. Makes the earliness concrete.
feedback_windowNoOptional: how long you can accommodate revisions on your current schedule — e.g. 'the next few days', 'this week'. Omit to leave open.
routeNofull_delivery (default) — everything is ready; early_preview — a first draft is ready earlier than expected, inviting feedback before the final.
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 are provided, so the description carries the full burden. It discloses that the tool does not count against monthly draft limit and explains the two routes and their outputs. While it could state whether it drafts or sends the email, the behavioral details are sufficient for an 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 front-loaded with the core purpose and scenario. Every sentence adds informative value, from the common mistake warning to the route explanation. It is efficiently structured without redundancy.

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?

With 7 parameters (2 required) and no output schema, the description covers all parameters with examples and context. It differentiates from a large set of sibling tools effectively. The email output is intuitive, so no further completeness is needed.

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 the description adds value beyond the schema by explaining the routes in detail ('full_delivery... confident announcement...', 'early_preview... inviting feedback...'), providing concrete examples for deliverables, and clarifying optional parameters like original_deadline and feedback_window with usage context.

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 starts with a clear verb+resource: 'Write the email when your work is ready ahead of the agreed deadline.' It explicitly distinguishes this tool from siblings like project_completion_email, project_handover_email, and milestone_approval_request_email, providing precise differentiation.

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?

The description explicitly states when to use the tool (work ready ahead of deadline) and when not to, contrasting with siblings. It also describes two routes (full_delivery and early_preview) with specific use cases, giving clear guidance on scenarios.

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