Skip to main content
Glama

retainer_check_in_email

Generates a monthly retainer check-in email that summarizes completed work, previews upcoming tasks, and invites clients to share new needs, creating natural upsell moments.

Instructions

Write a monthly check-in email to a retainer client. Summarises what was covered during the period, previews upcoming work, and opens the door to new needs — the natural upsell moment in an ongoing relationship. Keeps retainer relationships active without feeling like a report. Required: client_name, period (e.g. 'May', 'last month', 'Q2'). Optional: work_summary (1-2 lines of what you covered this period — omit to keep it brief and open), upcoming_work (what's planned next period — omit if not yet set), new_needs_question (a specific question to surface unmet needs, e.g. 'Are there any new campaigns or projects on your radar for next quarter?' — defaults to a general open-ended check), your_name. Workflow: retainer_proposal (close the deal) → project_kickoff_email (start) → retainer_check_in_email (monthly) → contract_renewal_email (renew). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
periodYesThe period this check-in covers (e.g. 'May', 'last month', 'Q2', 'the past few weeks')
work_summaryNoOptional: 1-2 line summary of what you covered or delivered this period (e.g. 'three blog posts, one email campaign, and the landing page revisions'). Omit to keep the check-in short and relationship-focused.
upcoming_workNoOptional: what you have planned or tentatively scheduled for the coming period (e.g. 'the product launch email sequence', 'two more posts and the monthly newsletter'). Omit if nothing is confirmed yet.
new_needs_questionNoOptional: a specific question to surface any new work or unmet needs (e.g. 'Are there any new campaigns or projects on your radar for next quarter?', 'Is there anything you'd like to prioritise differently going forward?'). Defaults to a general open-ended check if omitted.
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 carries full burden. It explains that the email summarises, previews, and opens door for upsell, and keeps relationships active without feeling like a report. It does not contradict any annotations (none provided). Missing details like auto-send but sufficient for an email draft 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?

Two efficient paragraphs: first outlines purpose and effects, second lists parameters with concise explanations plus workflow and draft limit note. No wasted words; every sentence adds value.

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 simplicity (email generation), the description is comprehensive: purpose, required/optional fields, defaults, workflow positioning, and draft limit. No output schema needed, so missing return value explanation is not a gap.

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 description adds value beyond schema by clarifying required vs optional, providing defaults (e.g., new_needs_question defaults to general open-ended check), and giving usage guidance for each parameter (e.g., 'omit to keep it brief and open').

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 explicitly states the tool writes a monthly check-in email to retainer clients, summarizing work, previewing upcoming work, and opening the door for upsells. It clearly distinguishes from sibling tools like 'client_check_in_email' by specifying 'retainer' and the monthly cadence.

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 lists required and optional parameters and provides a workflow sequence ('retainer_proposal → project_kickoff_email → retainer_check_in_email (monthly) → contract_renewal_email'), giving clear context on when to use it. It does not explicitly state when not to use or list alternatives, but the workflow implies its place.

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