Skip to main content
Glama

client_offboarding_email

Write a gracious, professional email to end an ongoing client relationship, preserving the connection for future referrals.

Instructions

Write a gracious, professional email ending an ongoing client relationship — a retainer, a long-term engagement, or a repeat working arrangement. Distinct from project_closure_email (a project that completed naturally) — this is for when you are choosing to end the relationship. The hardest email a freelancer has to write. Gets the tone right: clear and firm without blame, warm without being dishonest, and structured to preserve the relationship for future referrals. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
engagement_descriptionYesWhat you are ending (e.g. 'our monthly retainer', 'our ongoing content partnership', 'our working relationship')
final_dateYesWhen the engagement ends (e.g. 'June 30', 'end of this month', 'in 30 days')
outstanding_workYesWhat you will complete before the end date (e.g. 'the June content deliverables', 'the current sprint', 'nothing outstanding — all work is up to date')
reasonNoOptional: a brief, honest reason — keep it high-level (e.g. 'I am restructuring my practice to focus on a narrower service area', 'my capacity is changing', 'I need to reduce my client load'). Omit if there is no clean explanation.
offer_referralNoOptional: set to true to include an offer to recommend another provider. Default: false.
your_nameNoOptional: your name for the sign-off
Behavior3/5

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

No annotations are provided, so the description must convey behavior. It adds value by noting 'Does not count against your monthly draft limit', but it does not disclose whether the email is sent or just drafted, or any other side effects.

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?

The description is well-structured with key information front-loaded: purpose, sibling distinction, tone guidance, and draft limit detail. It is efficient but slightly verbose in the middle.

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?

For a tool with 7 parameters and no output schema, the description covers purpose, usage, tone, and draft limit context. It lacks explicit mention of output format but is otherwise 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?

Schema description coverage is 100%, so baseline is 3. The description does not elaborate on parameters beyond what the schema already provides, adding no extra meaning.

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 clearly states the tool writes an email ending a client relationship, specifies the relationship type (retainer, long-term engagement), and explicitly distinguishes from project_closure_email, leaving no ambiguity.

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?

The description provides clear usage context ('for when you are choosing to end the relationship') and names an alternative (project_closure_email). However, it omits exclusions and does not reference other relevant sibling tools like client_decline_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