Skip to main content
Glama

client_offboarding_checklist_email

Send a structured end-of-engagement email with a handover checklist covering completed work, asset transfer, outstanding actions, and system access changes to ensure nothing falls through the cracks.

Instructions

Write a structured end-of-engagement email that doubles as a practical handover checklist. Sent at project close or retainer end — covers what was completed, assets being transferred, outstanding actions for both sides, and any system access being revoked. Protects both parties by ensuring nothing falls through the cracks. Distinct from client_offboarding_email (which ends a relationship you chose to leave) and project_closure_email (a natural project wrap-up email) — this is the operational handover document with explicit action items and a checklist format. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name or company name
project_nameYesName of the project or engagement being closed (e.g. 'the Acme website redesign', 'our monthly SEO retainer')
deliverables_summaryYesBrief summary of what was completed during the engagement (e.g. 'full website redesign, content migration, and 3 months of SEO support')
assets_to_transferNoOptional: comma-separated list of files, accounts, or assets being handed over (e.g. 'source files, Google Analytics access, Figma project, GitHub repo'). Omit if nothing to transfer.
client_actionsNoOptional: things the client needs to action after handover (e.g. 'change shared passwords, accept Google Analytics transfer, update billing details'). Omit if none.
your_actionsNoOptional: anything you are still completing before the handover is fully done (e.g. 'final invoice to follow', 'source file export in progress'). Omit if everything is already done.
access_to_revokeNoOptional: systems or accounts you will lose access to or remove yourself from (e.g. 'Slack workspace, staging server, CMS admin'). Omit if none.
testimonial_askNoOptional: include a brief ask for a testimonial or LinkedIn recommendation at the end of the email. Default: true.
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 that the tool does not count against monthly draft limit and implies it creates an email draft. Additional behavioral details like permissions or side effects are not needed for a write 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?

Compact and front-loaded: purpose, usage context, sibling differentiation, and a behavioral note in three sentences. Every sentence adds value without redundancy.

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 clearly implies the tool returns an email draft. It covers purpose, scope, and differentiation from siblings. Slight gap: does not explicitly state the output format, but it's well-understood as an email generation tool.

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 description coverage is 100%, so baseline is 3. The description adds context about the overall structure but does not enhance individual parameter definitions beyond what the schema already provides.

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 structured end-of-engagement email with a handover checklist. It distinguishes from two sibling tools (client_offboarding_email and project_closure_email) by specifying this is an operational handover with action items and checklist format.

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?

Explicitly says 'Sent at project close or retainer end' and distinguishes from sibling tools, providing clear when-to-use and when-not-to-use guidance.

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