Skip to main content
Glama

scope_change_email

Write a professional email to notify a client when project work exceeds the original scope, outlining the impact and suggesting options like a change order or revised quote.

Instructions

Write a professional email to a client when work has grown beyond the original scope — new requests, added features, extra rounds of revisions. Raises the issue without accusation, outlines the impact, and presents options (change order, revised quote, or narrowing scope). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesThe client's first name
project_nameYesThe project name or description (e.g. 'the website redesign', 'your brand identity project')
scope_changeYesWhat has been added or changed beyond the original agreement (e.g. 'adding an e-commerce section to the website', 'three extra rounds of logo revisions', 'building a mobile app version')
original_scopeNoOptional: what was originally agreed (e.g. 'a 5-page brochure site', 'two logo concepts with one round of revisions'). Helps contrast clearly.
time_impactNoOptional: how much extra time this adds (e.g. '2–3 extra days', 'roughly a week of additional work')
cost_impactNoOptional: the additional cost or rate adjustment (e.g. '$800 at my standard day rate', 'an additional $1,200')
proposed_optionsNoOptional: the options you are offering the client (e.g. 'proceed with a change order, or scale the project back to the original scope'). If omitted, a standard two-option proposal is used.
your_nameNoOptional: your name for the sign-off
Behavior3/5

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

Description notes a behavioral trait (not counting against monthly draft limit) and implies a professional tone. However, it does not disclose whether the tool sends the email or merely generates text, nor does it mention required permissions or rate limits beyond draft count. No annotations are present, so the description carries the full burden but misses key side effects.

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?

Description is extremely concise and front-loaded. Three sentences cover purpose, content, and a key differentiator. Every sentence earns its place without redundancy.

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?

No output schema exists, so description should clarify what the tool returns. It implies the email text is generated but does not explicitly state the output format or behavior (e.g., whether it is saved, sent, or only returned). The description adequately covers the input scenario but leaves the output ambiguous.

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 baseline is 3. The description adds value by explaining the email's overall structure and tone (professional, non-accusatory, options-oriented). While it does not detail each parameter's role in the email, the schema already provides good per-parameter descriptions.

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?

Description clearly states the tool's purpose: writing a professional email about scope growth. It specifies the audience (client), trigger (work beyond original scope), and content (raises issue, outlines impact, presents options). This differentiates it from siblings like 'scope_clarification_email' (clarifying scope) and 'scope_warning_email' (warning about creep) by focusing on post-growth resolution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description tells when to use (scope growth) but does not explicitly say when not to use or mention alternatives. While the scenario is clear, there is no direct comparison to similar tools like 'change_order' or 'scope_clarification_email', leaving the agent to infer usage boundaries.

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