Skip to main content
Glama

project_resume_email

Write a professional email to restart a paused project after payment, client unblocking, or scheduled restart. Includes first concrete step and timeline note.

Instructions

Write a professional email restarting a paused project. Pairs with project_pause_email to complete the pause/resume lifecycle. Three routes: payment_received (default — payment has cleared, work is resuming; firm, professional, forward-looking; states the first concrete action so the client knows things are moving), client_unblocked (the missing items or information have now arrived; acknowledges receipt, notes any timeline adjustment, confirms next step), scheduled_restart (the agreed pause period has ended; warm reconnect, confirms restart, sets next milestone). Distinct from project_kickoff_email (starting fresh work) and project_closure_email (ending a project). Does not count against your monthly draft limit. Required: client_name. Optional: project_name, resume_date (when work is resuming — e.g. 'Monday', 'today', 'next week'), first_step (first concrete thing you'll do — e.g. 'I'll have the revised wireframes to you by Thursday', 'I'll pick up the development sprint'), timeline_note (any change to the overall deadline — e.g. 'we're still on track for the original July deadline', 'the revised delivery date is now 28 July'), route ('payment_received' | 'client_unblocked' | 'scheduled_restart' — default payment_received), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient first name
project_nameNoOptional: project name — e.g. 'the Hartley website', 'your brand refresh'. Makes the email specific.
resume_dateNoOptional: when work is resuming — e.g. 'today', 'Monday', 'next week'. Omit if you're just picking up immediately.
first_stepNoOptional: the first concrete action you'll take on restart — e.g. 'I'll have the revised wireframes to you by Thursday', 'I'll pick up the development sprint from where we left off'. Gives the client confidence that things are moving.
timeline_noteNoOptional: any change to the overall deadline — e.g. 'we're still on track for the original July deadline', 'the revised delivery date is now 28 July'. Omit if the timeline is unchanged and unambiguous.
routeNopayment_received (default) — payment cleared, resuming work; client_unblocked — the missing items have arrived, picking back up; scheduled_restart — agreed pause period is over, restarting.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits such as not counting against the monthly draft limit and describes the tone for each route. However, it does not specify any destructive actions or other side effects, which is appropriate for an email generation tool.

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?

The description is well-structured with an initial purpose statement, route details, and parameter explanations. It is slightly verbose but every sentence adds value, earning a score of 4.

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?

The description covers all seven parameters with examples, explains the three routes, and provides usage context. No output schema is present, but the description is sufficiently complete for an agent to use the tool effectively.

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 description coverage is 100%, so baseline is 3. The description adds meaningful context beyond schema, such as the default route, examples for first_step and timeline_note, and the purpose of each optional parameter, justifying a score of 4.

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's purpose: writing a professional email to restart a paused project. It specifies three distinct routes and distinguishes the tool from siblings like project_kickoff_email and project_closure_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?

The description provides explicit guidance on when to use the tool (resuming a paused project), pairs with project_pause_email for lifecycle, and explains when to choose each of the three routes. It also differentiates from sibling tools.

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