Skip to main content
Glama

meeting_cancellation_email

Write a professional email to cancel or reschedule a meeting with a client. Required details: client name and meeting description. Optional reason and proposed new time.

Instructions

Write a professional email to cancel or reschedule a meeting. Required: client_name, meeting_description (e.g. 'our Thursday check-in call', 'the kick-off meeting on Friday'). Optional: reason (brief, honest one-line — omit if no clean reason), action (default 'cancel' — use 'reschedule' to propose a new time), new_time (proposed replacement slot if rescheduling, e.g. 'next Tuesday at 2pm'), your_name. Pairs with meeting_request_email (scheduling) and meeting_recap_email (after a meeting that did take place). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
meeting_descriptionYesBrief description of the meeting being cancelled or rescheduled (e.g. 'our Thursday check-in call', 'the kick-off meeting scheduled for Friday at 10am', 'tomorrow's review call')
reasonNoOptional one-sentence reason for the cancellation (e.g. 'a scheduling conflict has come up', 'I have been unwell and need to reschedule', 'something urgent has arisen on another project'). If omitted, the email apologises without giving a reason — professional and always appropriate.
actionNoWhether you are cancelling outright ('cancel') or proposing to reschedule ('reschedule'). Default: 'cancel'.
new_timeNoProposed replacement time if rescheduling (e.g. 'next Tuesday at 2pm', 'any time next week that works for you', 'Thursday or Friday afternoon'). Omit if action is 'cancel' or if you want to leave it open.
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 notes a behavioral trait: 'Does not count against your monthly draft limit.' It does not contradict any annotations. It could explicitly state whether the email is drafted or sent, but the given context is sufficient for a drafting tool.

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?

Three sentences: first states purpose, second lists params, third mentions siblings and a constraint. No wasted words; front-loaded with key information.

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?

For a 6-parameter tool with no output schema, the description covers purpose, parameter details (required/optional), sibling relationships, and a special behavior (draft limit). It is complete enough for an agent to select and invoke the tool correctly.

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 coverage is 100% (baseline 3). The description adds value by rephrasing parameters in plain language and adding usage nuances (e.g., 'brief, honest one-line — omit if no clean reason' for reason), improving understanding 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 'Write a professional email to cancel or reschedule a meeting,' specifying the verb ('write') and resource ('email'). It distinguishes from siblings by naming 'meeting_request_email' and 'meeting_recap_email.'

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 links to related tools ('Pairs with meeting_request_email and meeting_recap_email') and specifies required parameters. It implies when to use via action enum (cancel/reschedule) but lacks explicit when-not-to-use or alternative selection 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