Skip to main content
Glama

expense_reimbursement_email

Write a professional email requesting reimbursement from a client for project expenses incurred on their behalf, including stock images, software, and travel.

Instructions

Write the professional email requesting reimbursement from a client for project expenses you have incurred on their behalf — stock images, fonts, software licences, hosting, printing, materials, travel. Required: client_name, expense_description (what you bought and why it was needed), amount. Optional: project_name, receipt_note (e.g. 'I have attached the receipt'), add_to_next_invoice (default false — if true, frames this as a heads-up addition to the next invoice rather than a standalone request), payment_instructions (e.g. 'via your usual payment portal', 'by bank transfer to the details on my invoice'), your_name. Distinct from budget_update_email (cost overrun from increased project scope or time) and invoice_cover_email (billing for your own labour). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or full name
expense_descriptionYesWhat you purchased and why it was needed for the project (e.g. 'a stock photography licence for the hero image', 'a Figma seat to collaborate on your design files', 'return travel to your office for the kick-off meeting')
amountYesThe amount to be reimbursed (e.g. '$85', '£120', '€200')
project_nameNoName or description of the project (e.g. 'the website redesign', 'your brand identity project')
receipt_noteNoOptional note about the receipt (e.g. 'I have attached the receipt for your records', 'receipt available on request'). If omitted, no receipt line is added.
add_to_next_invoiceNoIf true, frames the email as a transparency heads-up that this will appear on the next invoice, rather than a standalone reimbursement request. Default: false.
payment_instructionsNoHow you would like to be paid (e.g. 'via your usual payment portal', 'by bank transfer — details on my invoice', 'alongside the next milestone payment'). Omit if add_to_next_invoice is true.
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 explains the action (writing an email), the behavior of the add_to_next_invoice parameter, and mentions it does not count against a monthly draft limit. It doesn't explicitly state whether the email is sent or drafted, but the context is sufficient for a non-destructive email tool.

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 efficiently covers purpose, required/optional fields, and sibling distinctions. It is well-structured but could be slightly more organized with bullet points. Still very concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, 3 required, no output schema), the description adequately covers the email's purpose, parameter roles, and usage context. It could mention the output (e.g., generated email text) but that is implicitly clear 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% (baseline 3). The description adds meaning beyond the schema by explaining the purpose of key parameters like add_to_next_invoice (framing as invoice heads-up) and payment_instructions (omit when add_to_next_invoice is true).

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 a professional reimbursement email and distinguishes it from sibling tools budget_update_email and invoice_cover_email by specifying different use cases (project expenses vs. budget overruns vs. labor billing).

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 when-to-use guidance for reimbursement requests, lists required and optional fields, and differentiates from two sibling tools. It lacks explicit 'when not to use' but the sibling distinctions imply alternatives.

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