Skip to main content
Glama

rush_fee_email

Notify clients about rush fees for expedited delivery requests and obtain approval before proceeding. Clearly states the new deadline, additional charge, and coverage, prompting a quick yes/no response.

Instructions

Write the professional email notifying a client that their request for expedited delivery comes with a rush fee — and asking for approval before you start. States the accelerated deadline you can hit, the additional charge, and what it covers (weekend hours, rescheduled commitments, etc.), then makes a clear yes/no ask so the timeline doesn't slip further while waiting for a response. Keeps tone matter-of-fact and collaborative, not apologetic. Distinct from budget_update_email (cost overrun from project complexity), scope_change_email (client requests additional work), and project_extension_email (you requesting more time). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
rush_deadlineYesThe accelerated delivery date the client is requesting (e.g. 'Friday', 'end of day tomorrow', 'Wednesday 5pm')
rush_feeYesThe additional charge for rush delivery (e.g. '$400', '30%', '£250')
original_deadlineNoYour standard delivery timeline for this project (e.g. 'the end of next week', 'Wednesday the 18th') — named to make the acceleration concrete
project_nameNoName or description of the project (e.g. 'the landing page', 'your brand identity')
what_it_coversNoOne-line explanation of what the rush fee reflects — helps the client understand it is fair, not arbitrary (e.g. 'weekend hours and rescheduling two other client commitments', 'two late evenings to hit your deadline')
your_nameNoYour name for the sign-off
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the email's purpose, tone, and that it does not count against draft limit. However, it doesn't specify if the email is actually sent or just drafted, but given tool context (email generation), this is minor.

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?

One paragraph, front-loaded with purpose, then details, sibling differentiation, and draft limit note. Every sentence adds value, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With high schema coverage and no output schema, description fully explains the email's content, tone, and when to use. Includes note about draft limit, making it complete for an AI agent.

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 has 100% coverage with descriptions for all 7 parameters. The description adds overall context but doesn't provide additional meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states it writes a professional email about rush fee, names the specific action (write) and resource (email to client). Distinguishes from siblings like budget_update_email, scope_change_email, and project_extension_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 says when to use: notifying client about rush fee and asking for approval. Lists exact sibling alternatives and their use cases, guiding selection.

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