Skip to main content
Glama

mid_project_cancellation_response_email

Respond professionally when a client cancels a project mid-engagement. Summarize work completed, mention kill fee if applicable, and confirm final invoice.

Instructions

Write a professional response when a client cancels a project mid-engagement. Acknowledges the cancellation without drama, summarises work completed to date, states the kill fee amount if your contract includes one, and confirms the final invoice. Protects you professionally and financially by putting the key facts in writing. Distinct from project_pause_email (temporary stop), project_closure_email (natural end at completion), client_offboarding_email (relationship wind-down), and end_client_relationship_email (you ending it). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
project_nameYesName or brief description of the project (e.g. 'the website redesign', 'your brand identity')
work_completedYesSummary of what has been delivered or completed so far (e.g. 'wireframes, homepage design, and two interior page templates', 'discovery workshop, sitemap, and initial content strategy')
kill_fee_amountNoOptional: the kill fee amount or percentage from your contract (e.g. '$1,500', '50% of the remaining balance', '25% of total project fee'). If omitted, the email notes that a final invoice for work completed will follow without referencing a kill fee.
kill_fee_clauseNoOptional: brief reference to the contract clause covering cancellation (e.g. 'per clause 7 of our contract', 'as per our agreed terms'). Keeps the tone professional rather than confrontational.
final_invoice_totalNoOptional: total amount of the final invoice you will send (e.g. '$2,800'). Including this prevents surprises and frames the email as a clean close.
assets_to_handoverNoOptional: files, documents, or access you will hand over so the client can continue with another provider (e.g. 'source files, brand guidelines PDF, and CMS login credentials'). Offering a clean handover protects your reputation.
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 provided, so description carries full burden. It describes the content of the email but does not disclose if the tool sends the email, drafts it, or returns text. Lacks details on side effects or return format, though it implies a writing action.

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?

Four sentences, each serving a purpose: main action, key elements, sibling differentiation, and a usage note. Front-loaded and efficient with no wasted words.

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 the tool's moderate complexity (8 parameters, no output schema), the description explains purpose, content, and alternatives. It is nearly complete but could specify the return type (email text) and whether it sends the email.

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 good parameter descriptions. The tool description adds context about overall email structure but does not significantly enhance meaning beyond the schema. Baseline 3 applies.

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 it writes a professional response for mid-engagement cancellation, listing specific content like acknowledgment, work summary, kill fee, and final invoice. It also distinguishes from four sibling tools, providing a precise purpose.

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 states when to use (client cancels mid-engagement) and distinguishes from sibling tools with specific names and brief explanations. Also notes that it does not count against a monthly draft limit, adding practical 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