Skip to main content
Glama

project_restart_email

Draft a professional email to restart a paused project, acknowledging the pause and outlining next steps.

Instructions

Write a professional email restarting a paused project. Pairs with project_pause_email to complete the pause/resume lifecycle. Acknowledges the gap, confirms readiness, states the first concrete action, and addresses any timeline adjustments. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
project_nameYesThe project name or description
restart_reasonNoOptional: what cleared the way to restart (e.g. 'the budget has been approved', 'I've wrapped the other project', 'the feedback from your stakeholders is in'). Keep it brief — one clause.
first_actionYesThe first concrete thing you'll do to get moving again (e.g. 'send over a revised timeline by Wednesday', 'pick up from the homepage copy', 'schedule a quick catch-up call to re-align on priorities')
timeline_noteNoOptional: any adjustment to the original delivery timeline (e.g. 'the original deadline of July 15 still holds', 'I'll need to push the delivery by one week to July 22 to account for the pause')
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, but the description fails to disclose behavioral traits such as whether the email is actually sent or just generated, or any authentication requirements. It does mention the tool does not count against a monthly draft limit, which adds some transparency.

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 concise (5 sentences) and front-loaded with the primary purpose. Every sentence adds value without redundancy, achieving high density of useful 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?

Given the tool's complexity (6 parameters, 3 required, no output schema), the description is complete. It covers the tool's role, lifecycle relationship, email structure, and a notable constraint (draft limit). No gaps are apparent.

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 the baseline is 3. The tool description does not add significant meaning beyond the schema; it explains the email structure but does not augment parameter descriptions.

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 restart a paused project, with a specific verb and resource. It also distinguishes itself from the sibling project_pause_email, making its purpose unambiguous.

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 pairs this tool with project_pause_email, indicating it is used after a pause. This provides clear when-to-use and when-not-to-use guidance, and references an alternative tool.

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