Skip to main content
Glama

contract_renewal_email

Draft a professional contract renewal email before an engagement ends to keep clients re-booking. Choose same terms or propose rate changes with a revised route.

Instructions

Write a professional contract or retainer renewal email to send before an engagement ends. Most freelancers either ignore the end date and get caught off-guard when the client doesn't re-book, or wait until it's over before asking — both lose business. This email opens the renewal conversation at the right moment: references the work done, proposes continuing on the same or updated terms, and makes it easy for the client to say yes. Two routes: same_terms (renew at the same rate and scope — the default) and revised (propose a rate increase or scope change). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
contract_typeYesThe type of engagement being renewed (e.g. 'monthly retainer', 'quarterly contract', 'six-month engagement', 'annual support agreement')
end_dateNoOptional: when the current contract ends — makes the ask feel timely rather than random (e.g. 'end of June', 'July 31', 'in two weeks')
work_summaryNoOptional: one-line summary of what you've delivered — reminds the client of value before the ask (e.g. 'the rebrand and new website', 'four months of content strategy', 'the platform migration'). If omitted, the email references the engagement generically.
current_rateNoOptional (used with route=revised): the current rate or scope, so the client understands what is changing (e.g. '$3,000/month', '10 hours/week', 'two blog posts per month')
new_rateNoOptional (used with route=revised): the proposed new rate or scope (e.g. '$3,500/month', '15 hours/week'). If omitted with route=revised, the email proposes discussing updated terms rather than naming a number.
routeNosame_terms: propose renewing on the same rate and scope (default). revised: introduce a rate increase or scope change.
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 are provided, so the description carries the full burden. It discloses that the email opens the renewal conversation, references work done, and does not count against the draft limit. It explains the two routes and optional parameter behavior, offering good transparency.

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 two paragraphs, front-loaded with purpose. It includes some narrative detail ('Most freelancers...') which adds context but could be trimmed. Overall, every sentence contributes value, and it is well-structured.

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?

With 8 parameters, 2 required, and no output schema, the description is thorough. It covers all parameter roles, default behavior, optionality, and route implications. The agent has sufficient information to 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 valuable context beyond schema, such as explaining optional fields like end_date ('makes the ask feel timely'), work_summary ('reminds the client of value'), and new_rate behavior when omitted ('proposes discussing updated terms'). This enhances understanding.

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 contract or retainer renewal email. It specifies the verb 'write' and the resource 'renewal email,' and distinguishes itself from siblings by focusing on renewals. The two routes (same_terms/revised) provide specificity.

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 explains when to use this tool ('before an engagement ends') and provides context about common freelancer mistakes. It describes the two routes but does not explicitly exclude alternatives or state when not to use it. However, given the large sibling set, the differentiation is implicit.

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