Skip to main content
Glama

client_decline_email

Write a professional decline email for client project inquiries when capacity, fit, timing, or budget prevent acceptance. Maintains warmth and optionally suggests a referral.

Instructions

Write a professional email declining a client project inquiry — when you can't or shouldn't take the work. Covers four common situations: capacity (you're fully booked), not_fit (the project isn't the right match for your skills or style), timing (wrong timing — project start doesn't align), or budget (their budget doesn't meet your rates). Warm and respectful throughout: preserves the relationship, never burns a bridge. Optionally offers to refer them to someone better suited — turning a decline into goodwill. Most freelancers either ghost prospects or write awkward excuses; this is the professional middle path that keeps the door open for future work. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
project_nameNoName or short description of the project being declined (optional)
decline_reasonNoPrimary reason for declining: capacity (fully booked), not_fit (wrong match), timing (dates don't work), budget (below your rate). Defaults to capacity if omitted.
suggest_referralNoWhether to offer to pass their details to someone who might be a better fit (default true)
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 adds valuable behavioral context: the email is warm and respectful, preserves relationships, and does not count against monthly draft limit. It implies the tool generates a draft rather than sending it.

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 moderately concise, with the core purpose front-loaded. Each sentence adds value, though some minor redundancy (e.g., 'warm and respectful' repeated) could be trimmed.

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?

Without an output schema, the description covers essential aspects: purpose, scenarios, tone, optional referral, and draft limit. It does not explicitly state the output format (e.g., plain text), but the overall context is adequate.

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%, but the description enriches parameter meaning by explaining the four decline reasons (capacity, not_fit, timing, budget) and the optional referral, adding context beyond the schema.

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 declining a client project inquiry, covering four specific situations (capacity, not_fit, timing, budget). It distinguishes from sibling tools that handle other email types (e.g., bid_lost_follow_up, client_followup).

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 explains when to use the tool: when you can't or shouldn't take work, with scenarios listed. It implicitly indicates not to use for other purposes, but lacks explicit exclusions or alternative tool names.

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