Skip to main content
Glama

project_completion_email

Send a project completion email that confirms deliverables, thanks the client, and optionally requests a testimonial or suggests future work.

Instructions

Write a professional email to a client when you deliver the final output and close out a project. Confirms what's been delivered, thanks the client, and optionally asks for a testimonial and points toward future work. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
project_nameYesThe project name or description (e.g. 'the website redesign', 'your brand identity')
what_you_deliveredYesWhat you are handing over — be specific (e.g. 'the final logo files and brand guide', 'the live website and all source files', 'the completed reports and raw data export')
delivery_locationNoOptional: where you are sending or where they can find the deliverables (e.g. 'attached', 'in the shared Dropbox folder', 'via the WeTransfer link below')
highlightNoOptional: one thing you are particularly proud of or want to call out (e.g. 'the mobile animations turned out especially well', 'the new flow cut checkout steps from 6 to 2')
testimonial_requestNoOptional: whether to include a brief ask for a testimonial or review (default true). Set false to omit.
future_workNoOptional: mention of potential next steps or future work (e.g. 'I would love to help with the next phase', 'if you ever need ongoing support, I am available')
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 must carry the burden. It discloses that the tool 'does not count against your monthly draft limit,' which is a key behavioral detail. It doesn't mention automation or permissions, but the core behavior (generating an email) is transparent.

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?

Extremely concise: a few sentences that front-load the purpose and quickly list key components. No wasted words, easy to scan.

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 8 parameters (3 required), no output schema, and no annotations, the description covers the essential context: what the email contains, optional elements, and a notable behavioral detail. It does not address return values or error states, but for a simple email tool, it is sufficiently complete.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no additional parameter details beyond the schema; it focuses on overall purpose. No extra semantic value provided for parameters.

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 describes the tool's purpose: writing a professional email when delivering final project output and closing out a project. It specifies contents like confirming deliverables, thanks, optional testimonial and future work, distinguishing it from related tools like milestone_delivered_email or project_closure_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?

States when to use (final delivery and closure) and what the email includes. While it doesn't explicitly list when not to use or name alternatives, the context is fairly clear given the sibling list. A slight gap in explicit usage boundaries prevents a 5.

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