Skip to main content
Glama

proposal_expiry_reminder_email

Sends a reminder email when a proposal is nearing or past its expiry date, with options for a gentle nudge, firm deadline, or extension offer to re-engage the prospect.

Instructions

Write the follow-up email sent when a submitted proposal is approaching — or has reached — its expiry date. Its job: create urgency without pressure, surface any blockers holding up the decision, and keep the door open. Distinct from client_followup (general chasing of a sent proposal with no deadline angle), bid_lost_follow_up (for when you've already lost), and post_discovery_follow_up_email (sent right after a call, before the proposal is written). Three routes: gentle_nudge (default — soft check-in asking if they have questions before the deadline, no hard pressure), firm_deadline (clear statement of expiry, direct ask for a decision — use when the deadline is tomorrow or already passed), extend_offer (proactively offer to extend the deadline if they need more time — use when you'd genuinely rather wait than lose the deal). Required: client_name (prospect's first name), proposal_topic (what the proposal covers — e.g. 'brand identity project', 'Q3 development retainer', 'website redesign'). Optional: expiry_date (when the proposal expires or expired — e.g. 'Friday', 'June 27', 'yesterday'; if omitted, the email references 'the proposal' generically), proposal_value (total value or rate — e.g. '$8,500', '$4,200/mo'; if provided, re-anchors the investment in the reader's mind), route, your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe prospect's first name
proposal_topicYesWhat the proposal covers — e.g. 'brand identity project', 'Q3 development retainer', 'website redesign'. Used to personalise the subject and body.
expiry_dateNoOptional: when the proposal expires or expired — e.g. 'Friday', 'June 27', 'yesterday'. If omitted, the email references the proposal generically without a hard date.
proposal_valueNoOptional: the total value or rate in the proposal — e.g. '$8,500', '$4,200/mo'. If provided, re-anchors the investment in the prospect's mind.
routeNogentle_nudge: soft check-in asking if they have questions before the deadline — default for most situations. firm_deadline: clear statement of expiry, direct ask for a decision — use when the deadline is tomorrow or already passed. extend_offer: proactively offer to extend if they need more time — use when you'd rather wait than lose the deal.
your_nameNoOptional: your 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. Discloses tool creates an email, does not count against monthly draft limit, and has three behavioral routes. Lacks explicit statement on side effects (e.g., whether email is saved or sent) but otherwise transparent.

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?

Description is long but well-structured: starts with purpose, then sibling differentiation, route explanations, parameter details, and end note. Every sentence adds value, but some phrases (e.g., 'Its job: create urgency...') are slightly redundant.

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

Completeness3/5

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

No output schema provided, but description does not explain what the tool returns (e.g., generated email text or draft). Missing output specification for a tool with multiple routes. Other aspects (parameters, routes) are well-covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, meaning description adds value beyond schema. For route, it explains usage per enum value; for proposal_value, it states re-anchors investment; for expiry_date, clarifies behavior if omitted. Enriches parameter meaning.

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 explicitly states tool writes follow-up emails for proposals approaching or past expiry. It names three routes and clearly distinguishes from three sibling tools (client_followup, bid_lost_follow_up, post_discovery_follow_up_email) with specific differences.

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?

Provides explicit when-to-use guidance for each route: gentle_nudge as default, firm_deadline when deadline is tomorrow/past, extend_offer when willing to wait. Also notes tool is for submitted proposals. Distinguishes from siblings with clear context.

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