Skip to main content
Glama

project_closure_email

Write a professional email to close a completed project, confirming deliverables, addressing handover items, and expressing thanks while suggesting future work opportunities.

Instructions

Write the final email when a project is fully delivered and complete. Confirms what was delivered, handles any handover items, expresses genuine thanks, and plants seeds for future work. Different from project_kickoff_email (which starts the engagement) — this closes it professionally. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
your_nameYesYour name (sign-off)
client_nameYesThe client's first name
project_nameYesBrief name or description of the project (e.g. 'the Acme Corp website redesign', 'the brand identity project')
what_was_deliveredYesWhat you delivered — list the key deliverables (e.g. '5-page Webflow site, style guide, mobile-optimised')
handover_itemsNoOptional: anything the client still needs to action (e.g. 'update your DNS records', 'add your own copy to the About page', 'set your own admin password')
warranty_periodNoOptional: any support or bug-fix period you're offering (e.g. '14 days of bug fixes included', '30-day support window')
future_work_hookNoOptional: a natural next-step or future work opportunity to mention (e.g. 'SEO setup', 'quarterly content updates', 'Phase 2 mobile app')
Behavior4/5

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

No annotations provided, so description carries the full burden. It discloses the action (writes a closing email) and adds a useful behavioral trait ("Does not count against your monthly draft limit"). No contradictions or missing critical safety info.

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?

Three sentences, front-loaded with purpose, no redundant information. Every sentence adds value.

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?

The description adequately explains the tool's purpose and behavior for a simple email generation tool. It does not describe the return value (the email text), but that is implicit. Could mention that it generates a draft.

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 parameter descriptions. The description adds context about the email's purpose but does not provide additional detail beyond what the schema already states for individual 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?

The description uses a specific verb ("Write the final email") and resource ("project closure email"), lists the content elements (confirms delivery, handover, thanks, future work), and explicitly distinguishes from the sibling project_kickoff_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?

Clearly states when to use ("when a project is fully delivered and complete") and differentiates from project_kickoff_email. However, it does not mention other related siblings like project_completion_email or project_handover_email.

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