Skip to main content
Glama

end_client_relationship_email

Write professional emails to end client relationships or retainers with options for natural end, capacity issues, or fit mismatch. Clear, direct, and warm where appropriate.

Instructions

Write a professional email to end an existing client relationship or retainer. Three modes: natural_end (the engagement has run its course — use when the project is done and you're not renewing; warm, leave the door open for future work), capacity (you genuinely don't have room to continue — honest, no blame, brief), fit_mismatch (the working relationship isn't working — handled carefully; professional and final without being cold or over-explaining). Most freelancers write these too apologetically (which reads as uncertain) or too abruptly (which burns the bridge). This tool finds the professional middle: clear, direct, warm where appropriate. Required: client_name. Optional: engagement_description (what you've been doing together — e.g. 'the monthly retainer', 'the content work', 'the design contract'), end_date (when the engagement ends — e.g. 'end of this month', 'June 30', 'after the current milestone'), reason (natural_end | capacity | fit_mismatch — defaults to natural_end), handover_note (optional: what you're doing to wrap up or help them transition — e.g. 'I'll deliver the final files by Friday', 'happy to brief a replacement'), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name
engagement_descriptionNoOptional: what you've been doing together — e.g. 'the monthly retainer', 'the content work', 'the design contract', 'our arrangement'. Helps make the email specific rather than generic.
end_dateNoOptional: when the engagement ends — e.g. 'end of this month', 'June 30', 'after the current milestone is delivered'. If omitted, the email stays slightly open on timing.
reasonNonatural_end (default — engagement has run its course; warm and future-friendly), capacity (you don't have room to continue; honest, brief, no blame), fit_mismatch (working relationship isn't working; professional and final, avoids over-explaining).
handover_noteNoOptional: what you're doing to wrap up or help them transition — e.g. 'I'll deliver the final files by Friday', 'happy to brief a replacement if that's useful', 'everything is documented in the shared folder'. Including a handover gesture is good professional practice and often softens the message.
your_nameNoYour name for the sign-off
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the tool's behavior: it writes an email, has three modes, and does not count against a monthly draft limit. It does not mention auth requirements or rate limits, but those are unlikely for a text generation tool. The behavioral context is adequate.

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, starting with the main purpose, then detailing modes, required/optional params, and tone advice. It is slightly lengthy but every sentence adds value. A 5 would require more conciseness without losing clarity.

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 6 parameters, 3 modes, and no output schema, the description is quite complete: it covers all parameters with examples and defaults, explains the three modes, and provides professional best practices. It does not describe the return format, but that is implicitly the email text. A 5 would require more explicit handling of edge cases or output specification.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the reason parameter's enum values, giving examples for engagement_description and handover_note, and clarifying defaults (reason defaults to natural_end). This extra context justifies a 4.

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 a professional email to end a client relationship or retainer, and distinguishes three specific modes (natural_end, capacity, fit_mismatch) with distinct use cases. This makes the purpose highly specific and differentiates it from sibling tools like client_check_in_email or project_pause_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?

The description provides explicit guidance on when to use each mode (natural_end for completed projects, capacity for lack of room, fit_mismatch for poor fit) and offers tone advice. However, it does not explicitly state when not to use this tool or mention alternatives from the sibling list, which keeps it from 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