Skip to main content
Glama

client_material_chase_email

Send a professional email to chase overdue client materials or approvals, automatically adjusting tone based on days overdue to keep projects on track.

Instructions

Write a professional email chasing a client for overdue materials, content, or approvals needed to continue the project. Used when the client hasn't delivered what they committed to — content, feedback, access, sign-off — and the delay is blocking your work. Calibrates tone based on how overdue they are: friendly (1–5 days), firm (6–14 days), or escalation (15+ days). Makes the impact clear without blame. Distinct from project_delay_warning (when YOU are delayed), payment_reminder_email (financial), and third_party_delay_email (external vendor delay). 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 (e.g. 'the website redesign', 'your brand identity project')
what_is_neededYesExactly what you're waiting for — be specific (e.g. 'the copy for the About and Services pages', 'approval on the logo concepts', 'admin access to the WordPress dashboard', 'sign-off on the revised scope document')
original_due_dateNoOptional: when you were expecting these materials (e.g. 'last Tuesday', 'June 12th', 'two weeks ago'). Including this makes the email more concrete.
days_overdueNoOptional: how many days overdue. Used to calibrate tone — 1–5 = friendly, 6–14 = firm, 15+ = escalation. If omitted, defaults to friendly.
impactNoOptional: what delay this is causing (e.g. 'I can't start the build phase without it', 'the launch date will slip if we don't receive this this week', 'your slot in my schedule is at risk'). Keeps the email factual rather than a complaint.
new_deadlineNoOptional: the new date you need the materials by to stay on track (e.g. 'by end of day Friday', 'by June 20th'). Giving a clear target makes it easier for the client to act.
your_nameNoOptional: your name for the sign-off
Behavior5/5

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

Despite no annotations, the description fully discloses key behaviors: tone calibration (friendly/firm/escalation), making impact clear without blame, and that it does not count against monthly draft limit. No contradictions.

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?

Five well-structured sentences, each adding value: purpose, usage, tone, sibling distinctions, and behavioral note. Front-loaded with main action. No unnecessary words.

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 8 parameters (3 required), no output schema, and no annotations, the description thoroughly covers purpose, usage, behavioral nuance, and parameter explanations. It provides sufficient context for correct invocation.

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 detailed parameter descriptions. The overall description adds context on tone calibration and usage, but the individual parameter descriptions already provide semantics. Slightly redundant but still valuable.

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?

Clearly states the tool writes a professional email for chasing overdue materials/content/approvals. Distinguishes from siblings like project_delay_warning, payment_reminder_email, and third_party_delay_email, providing specific verb+resource and context.

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 describes when to use: when client hasn't delivered committed items and delay blocks work. Mentions tone calibration based on overdue days and names alternative tools for different scenarios.

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