Skip to main content
Glama

capacity_waitlist_email

Write a professional waitlist email to prospects when you're fully booked. Acknowledges their enquiry, explains your capacity, and offers first priority when your schedule opens.

Instructions

Write a professional email to a prospect when you're fully booked but don't want to lose them. Parks them warmly — acknowledges their enquiry, explains you're at capacity, gives an availability window (if known), and offers first priority when your schedule opens. Most freelancers either decline (and lose the prospect for good) or go silent (worse). This is the professional middle path that creates a warm pipeline for your next available slot. Required: client_name. Optional: project_description (what they came to you about — makes the email feel specific rather than templated), available_from (when you'll next have capacity, e.g. 'mid-July', 'early Q4', 'end of August' — omit if uncertain), offer_priority_slot (default true — offers to confirm intent now so you can hold the slot when it opens), your_name. Distinct from client_decline_email (permanent no for fit/budget reasons) and reactivation_email (following up on a cold prospect). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
project_descriptionNoOptional: brief description of what they want to hire you for (e.g. 'the website redesign', 'your brand identity project', 'the copywriting work you mentioned'). Makes the email feel specific rather than a generic 'I'm busy' note.
available_fromNoOptional: when you'll next have capacity (e.g. 'mid-July', 'early Q4', 'the end of August', 'late September'). Omit if genuinely uncertain — the email handles that case gracefully.
offer_priority_slotNoWhether to offer to hold a priority slot for the prospect when your calendar opens. Default true — include the offer unless you're not sure you want the work.
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 bears the full burden. It discloses behavioral traits: parks the prospect warmly, acknowledges inquiry, explains capacity, gives availability if known, offers priority slot. Also mentions it doesn't count against monthly draft limit. Missing: whether it sends or just generates the email text.

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?

Two paragraphs with front-loaded purpose. Every sentence provides useful information, no fluff. Could be slightly more concise but well-organized.

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?

Covers purpose, usage, parameters, and behavioral notes. Lacks explicit mention of output format (e.g., what the email text looks like) or error handling, but given no output schema, the description is fairly complete for a simple email generation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and description adds valuable context beyond schema descriptions, e.g., for project_description it clarifies 'makes the email feel specific rather than a generic I'm busy note.' Provides usage nuance for optional fields like available_from and offer_priority_slot.

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 a prospect when fully booked, with a specific verb 'Write' and resource 'email', and distinguishes from sibling tools like client_decline_email and reactivation_email.

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 tells when to use (fully booked but don't want to lose prospect), when not to use (permanent no), and names two alternatives (client_decline_email, reactivation_email). Also explains that it creates a warm pipeline rather than declining or going silent.

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