Skip to main content
Glama

client_anniversary_email

Draft a warm, short email to mark the anniversary of working with a long-term client. Acknowledge the relationship without a pitch or deliverables list to strengthen the partnership.

Instructions

Write a short, warm email marking the anniversary of working with a long-term client — 1 year, 2 years, or any meaningful milestone. Different from annual_review_email (which summarises deliverables and results in a structured retrospective) — this is the relationship-first touchpoint that makes a client feel like a long-term partner, not a transaction. No deliverables list, no pitch, no ask. Just a genuine acknowledgment of the working relationship and a light forward-looking line. Under 100 words. The goal is to be memorable and human, not to upsell — though it naturally positions you top-of-mind when their next need arises. Required: client_name, milestone (e.g. '1 year', '2 years', '18 months'). Optional: project_or_relationship (what you've worked on together — a named project or 'our work together' — makes the milestone feel specific), standout_moment (one specific thing from the relationship worth acknowledging — a result, a challenge you solved, a moment that stood out), forward_line (a single sentence looking ahead — what you're looking forward to, or an open door for what comes next), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name
milestoneYesThe anniversary milestone (e.g. '1 year', '2 years', '18 months', '3 years')
project_or_relationshipNoOptional: what you've worked on together — a named project ('the site redesign'), an ongoing relationship ('our work together'), or a category ('the branding work'). Makes the milestone feel specific rather than generic.
standout_momentNoOptional: one specific thing from the relationship worth acknowledging — a result ('the campaign that hit 3x target'), a challenge you solved together ('getting through the launch crunch'), or a moment that stood out ('the direction pivot that ended up being the right call'). Omit if nothing obvious fits.
forward_lineNoOptional: a single sentence looking ahead — what you're looking forward to ('looking forward to what we build this year'), an open door ('if there's anything you're thinking about for next year, I'd love to hear it'), or just warmth for the future. Omit to let the email close naturally.
your_nameNoYour name for the sign-off
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses that the tool generates a non-upsell, human-toned email under 100 words with optional personalization fields. States it does not count against monthly limit. No mention of side effects or authentication, but for a generation tool this is sufficient.

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 roughly 150 words, well-structured with front-loaded purpose and differentiation. Every sentence adds information without redundancy. Minor length could be trimmed, but overall efficient.

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

Completeness4/5

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

Given no output schema, description adequately explains the nature of the output (email under 100 words, warm, no pitch). It covers usage, parameter nuance, and differentiation. Could include edge cases like milestone format flexibility, but not essential for basic usage.

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 covers 100% of parameters with descriptions. The description adds value by explaining how optional parameters (project_or_relationship, standout_moment, forward_line) contribute to specificity and warmth, going beyond basic schema definitions.

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 short, warm anniversary email for long-term clients, distinguishes from sibling annual_review_email, and specifies constraints (no pitch, no ask, under 100 words). The verb 'Write' plus resource 'email marking anniversary' makes it 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?

Explicitly contrasts with annual_review_email, stating this is relationship-first with no deliverables or pitch. Provides when-to-use (anniversary acknowledgment) and when-not-to (structured retrospectives). Also mentions it doesn't count against monthly draft limit, adding practical 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