Skip to main content
Glama

budget_update_email

Write an email to inform a client that your project estimate was too low, presenting the original and updated cost, a brief honest reason, and asking how they would like to proceed.

Instructions

Write the email informing a client that the project will cost more than originally estimated — due to unforeseen technical complexity, third-party cost increases, or scope that proved harder than anticipated. This is distinct from scope_change_email (client requested extra work) and budget_proposal (client said your quote was too high): this is the honest update when your own estimate turns out to be off, and you need to raise the number before proceeding. Structure: clear statement of original vs. updated figure, a brief honest reason (one sentence — not an essay), and a question asking how they'd like to proceed before you go further. Tone: direct and professional, not grovelling or defensive. Most freelancers either absorb the cost silently or surprise clients with a higher invoice — this is the professional middle path that respects the client's budget and your rate. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
project_nameNoName of the project
original_estimateYesThe original cost estimate (e.g. '$2,500' or '20 hours')
updated_costYesThe revised cost or estimate (e.g. '$3,200' or '28 hours')
reasonNoBrief explanation for the increase — e.g. 'the integration required a custom solution we didn't anticipate', 'the third-party API pricing changed'. One sentence max.
approval_neededNoWhether to ask for client approval before proceeding (default true — always recommended)
your_nameNoYour name for the sign-off
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It describes the email's purpose, structure, and tone, and notes that it does not count against the monthly draft limit. However, it is somewhat ambiguous whether the tool actually sends the email or just generates the text, which could be clarified.

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?

The description is a single paragraph that is well-organized and informative, but slightly verbose. It efficiently conveys all necessary information without significant redundancy.

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?

Given the 7 parameters, 3 required, and no output schema, the description comprehensively covers the tool's behavior, usage context, and output expectations. It includes comparison to siblings, structure guidance, tone, and a note about draft limits, making it fully adequate for an AI agent.

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%, and the description adds value by explaining the context for parameters like 'reason' (one sentence max) and 'approval_needed' (default true). This goes beyond the schema definitions to guide the AI on proper usage.

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 an email about a budget increase due to underestimation. It explicitly distinguishes from sibling tools like scope_change_email and budget_proposal by specifying the scenario of an honest estimate correction.

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?

The description provides explicit when-to-use guidance (honest update when estimate is off) and when-not-to-use (scope changes or budget proposals). It also outlines the recommended structure and tone, giving clear instructions for appropriate use.

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