Skip to main content
Glama

scope_creep_email

Draft a professional, non-confrontational email to address out-of-scope client requests, clarify scope boundaries, and offer change orders or quotes without apologizing.

Instructions

Write a professional, non-confrontational email addressing a client request that falls outside the agreed project scope. The email acknowledges the request positively, clarifies the scope boundary, and offers a change order or quote for the additional work — without apologising for sticking to the agreement. Handles one of the most common and professionally charged situations for freelancers: when a client treats 'out of scope' as optional. Required: client_name, project_name, scope_change_description. Optional: original_scope_note (what was agreed), quoted_fee (if you already have a price), timeline_impact (if extra work affects delivery), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
project_nameYesName or brief description of the project
scope_change_descriptionYesWhat the client is asking for that falls outside the original scope (e.g. 'adding a third language to the website', 'redesigning the mobile app in addition to the desktop version', 'writing product descriptions for 50 additional SKUs')
original_scope_noteNoOptional: brief reminder of what the original scope covered, for context (e.g. 'the agreed scope covers the five-page website in English only', 'the project covers the desktop web app only as outlined in the proposal'). If omitted, a generic scope boundary reference is used.
quoted_feeNoOptional: the additional fee for the out-of-scope work if you already know it (e.g. '$450', '£800', '6 hours at my standard day rate'). If provided, the email includes the quote directly. If omitted, the email offers to send a change order.
timeline_impactNoOptional: how the additional work would affect the current delivery timeline (e.g. 'push the delivery date by 3 days', 'require an extended deadline to the end of the month'). If omitted, no timeline impact is mentioned.
your_nameNoOptional: your name for the sign-off
Behavior5/5

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

No annotations provided, so the description fully covers behavior. It details the tone (professional, non-confrontational), structure (acknowledge, clarify boundary, offer change order/quote), and constraints (does not apologize). No destructive behavior is relevant; the tool drafts an email without sending.

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?

Five sentences efficiently convey the tool's purpose, tone, and parameter list. Front-loaded with the main verb and context, every sentence adds value. Slightly longer than necessary but well-structured and clear.

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?

The description is thorough for a generative tool with no output schema: it covers purpose, behavior, parameters, and usage notes (no monthly limit). No missing critical information given the tool's simplicity.

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

Parameters5/5

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

Schema description coverage is 100%, and the tool description adds significant value by explaining parameter usage with examples (e.g., scope_change_description examples, purpose of optional fields). It clarifies how each parameter influences the output, exceeding schema alone.

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's purpose: writing a professional, non-confrontational email for out-of-scope client requests. It explicitly distinguishes from siblings like scope_change_email and scope_warning_email, and provides specific context about the common freelancer situation.

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 indicates when to use the tool (client request outside scope) and includes a note about not counting against monthly draft limit. However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance, missing some comparative direction.

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