Skip to main content
Glama

referral_thank_you_email

Write a personalized thank-you email acknowledging a client referral, expressing genuine appreciation, and optionally offering to return the favor.

Instructions

Write a warm, genuine thank-you email to someone who referred a new client to you. Acknowledges the specific referral, expresses genuine appreciation without being gushing, and optionally offers to return the favour. Works whether the project is just starting, underway, or completed. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referrer_nameYesFirst name of the person who made the referral
new_client_nameYesName of the person or company they referred (e.g. 'Sarah', 'the team at Acme') — makes the email specific rather than generic
project_typeNoOptional: brief description of the work (e.g. 'brand identity project', 'website redesign', 'strategy consultancy'). Adds specificity without oversharing client details.
outcomeNoOptional: how the engagement went, if it has started or concluded (e.g. 'we kicked off last week and it's going well', 'we wrapped up and the client was delighted'). Omit if you're writing before work has begun.
offer_backNoOptional: whether to explicitly offer to return the favour by referring work to them or recommending them. Default: false.
your_nameNoOptional: your name for the sign-off
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool acknowledges the referral, expresses appreciation, and may offer to return the favor. It also notes the draft limit benefit. However, it does not clarify whether the tool sends the email or just drafts it, nor any side effects or permissions needed, leaving some ambiguity.

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?

The description is four sentences, each contributing value: purpose, content details, versatility, and a unique benefit. It is front-loaded with the primary function, with no unnecessary words.

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?

Given the tool has 6 parameters and no output schema, the description covers the purpose and partial behavior but does not explain the output format (e.g., returns email text, sends it, or saves to drafts). It also lacks prerequisites or error handling. This leaves gaps for a complete understanding.

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

Parameters3/5

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

Schema description coverage is 100%, with all 6 parameters documented in the schema. The description adds no additional parameter-level details beyond the schema, so the baseline of 3 is appropriate.

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 'Write a warm, genuine thank-you email to someone who referred a new client to you', specifying a verb and resource. Among siblings, it is distinct from referral_request (which asks for referrals) and referral_thank_you (possibly a shorter variant), so it is well-differentiated.

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 provides clear context on when to use: after a referral, and it works at any project stage. It also notes the tool does not count against draft limits. However, it does not explicitly exclude alternatives or state when not to use it, lacking full guidance.

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