Skip to main content
Glama

out_of_office_email

Send a proactive leave notice to clients before time off. Set clear dates, response expectations, and urgent contact info without apologizing.

Instructions

Write a professional heads-up email to clients before you go on leave. Confident and matter-of-fact — doesn't apologize for taking time off. Sets clear expectations on dates, response time, and what (if anything) to do for urgent matters. Different from an auto-reply: this is the proactive note you send to active clients a few days before you leave. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
start_dateYesFirst day you're away (e.g. 'Monday June 16', 'June 16')
end_dateYesLast day you're away (e.g. 'Friday June 27', 'June 27')
return_dateYesFirst day back — when they can expect a response (e.g. 'Monday June 30', 'June 30')
project_statusNoOptional: note about ongoing work — reassures client everything is in hand (e.g. 'the first draft will be with you before I leave', 'your project is on track and nothing is scheduled during this period', 'I'll complete the homepage before I go')
urgent_contactNoOptional: who or how to reach someone for genuine urgencies (e.g. 'for anything genuinely urgent, email my colleague at colleague@example.com', 'I'll have limited access and will check messages once a week')
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 are provided, so the description carries full burden. It notes the tool does not count against draft limit, but does not disclose other behavioral traits such as whether it sends immediately, requires authentication, or is destructive. Some transparency is present but incomplete.

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?

The description is four sentences with no wasted words. It front-loads the purpose, provides tone guidance, usage context, and a clear differentiator. Every sentence adds value.

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?

For a tool with 7 parameters (4 required) and no output schema, the description provides adequate context: it explains the email's purpose, tone, timing, and differentiator. It covers the essential aspects, though it could mention sending mechanism or limitations.

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 description coverage is 100%, so each parameter already has a description. The tool description adds overall tone and usage context but does not provide additional per-parameter semantics beyond what the schema already provides. 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?

The description clearly states the tool writes a professional heads-up email before leave, explicitly distinguishing it from an auto-reply. It uses a specific verb ('write') and resource ('heads-up email') and provides enough context to differentiate from siblings.

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?

The description explicitly states when to use the tool: proactive note to active clients a few days before leave. It distinguishes from auto-reply and mentions that it does not count against monthly draft limit, providing clear guidance on usage and alternatives.

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