Skip to main content
Glama

revision_response_email

Draft client email responses to revision requests. Supports in-scope revisions, exceeded rounds, or out-of-scope changes with clear next steps.

Instructions

Write the email responding to a client's revision request. Three modes: 'in_scope' (happy to revise — confirms what you'll change and when), 'exceeds_rounds' (they've used their included revision rounds — explains what's included and what additional rounds cost), 'out_of_scope' (the request is a direction change that requires a change order, not a revision). Distinct from scope_change_email (formal change order) and scope_warning_email (early creep flag) — this is the specific, policy-in-action response to a concrete revision ask. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
revision_typeYes'in_scope': revision is within agreed rounds — you'll do it; 'exceeds_rounds': they've used up their included rounds — additional work costs more; 'out_of_scope': it's a direction change, not a revision — needs a change order
project_nameNoOptional: the project name (e.g. 'the brand identity', 'the website redesign')
revision_requestNoOptional: brief description of what the client wants changed (e.g. 'swap the colour palette to navy and gold', 'rewrite the homepage copy in a more casual tone'). Makes the response feel specific rather than templated.
rounds_includedNoOptional: number of revision rounds included in the original agreement (e.g. 2). Used in 'exceeds_rounds' mode.
rounds_usedNoOptional: how many rounds have already been used (e.g. 2). Used in 'exceeds_rounds' mode.
estimated_costNoOptional: cost for an additional revision round (e.g. '$300', '2 hours at my hourly rate'). Used in 'exceeds_rounds' mode.
turnaroundNoOptional: when you'll have the revision back (e.g. 'by Thursday', 'within 2 business days'). Used in 'in_scope' mode.
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 present, so description carries full burden. It explains the tool generates email text and mentions it doesn't count against draft limit. Lacks details on potential side effects or permissions, but for a generative email 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three well-structured sentences with no redundancy. Every sentence adds critical context about modes, distinctions, and usage limits.

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?

Covers purpose, all three modes, sibling tool differentiation, and draft limit. No missing context for an email generation tool.

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% with good parameter descriptions. Description adds value by explaining how parameters relate to the three modes and which are used in each context, going beyond the schema.

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 states the tool writes an email responding to a revision request and specifies three modes with clear explanations. It distinguishes itself from sibling tools, making the purpose unmistakable.

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 scope_change_email and scope_warning_email, and describes when each mode applies. Provides clear guidance on tool selection.

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