Skip to main content
Glama

spec_work_decline_email

Politely decline unpaid spec work requests while preserving client relationships. Redirect to your portfolio or counter with a paid discovery session as a constructive alternative.

Instructions

Decline a request to produce work on spec (unpaid design, copy, or code samples produced as part of a pitch or evaluation) without burning the relationship. Two routes: decline (default — firm but warm no; redirects to your existing portfolio and process; use when you don't want to propose an alternative), counter (no to spec, yes to a small paid discovery or test engagement as the right first step — use when you're genuinely interested in the project but won't work for free). Distinct from competitor_response_email (you've already been engaged and the client is comparing providers), client_decline_email (you're turning down the whole project), and proposal_expiry_reminder_email (chasing a submitted proposal). Does not count against your monthly draft limit. Required: client_name. Optional: project_description (what the spec request was for — e.g. 'a sample homepage design', 'a draft chapter', 'a prototype feature'), portfolio_url (link to existing work — include so the client can self-qualify), discovery_offer (the paid alternative you're proposing — e.g. 'a paid half-day discovery workshop', 'a two-hour paid strategy session', 'a small paid scoping engagement'; default 'a paid discovery session'), route ('decline' | 'counter' — default decline), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient first name or company name
project_descriptionNoOptional: what the spec request was for — e.g. 'a sample homepage design', 'a draft chapter', 'a prototype feature'. Makes the email specific rather than generic.
portfolio_urlNoOptional: URL to your existing portfolio, case studies, or work samples — e.g. 'mysite.com/work'. Including this gives the client a clear next step to evaluate fit without spec work.
discovery_offerNoOptional (counter route only): the paid alternative you're offering — e.g. 'a paid half-day discovery workshop', 'a two-hour paid strategy session', 'a small paid scoping engagement'. Default: 'a paid discovery session'. Only used when route is counter.
routeNodecline (default) — warm, firm no to spec, redirect to portfolio, keep door open; counter — no to spec but offer a paid alternative engagement as the first step.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the tool does not count against monthly draft limit and explains behavioral outcomes of two routes. Could mention sending behavior or further 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is detailed but efficient, front-loading purpose and routing, then parameters. Each sentence adds value; no redundancy. Could slightly streamline parameter explanations but overall excellent.

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 6 parameters, no output schema, description covers all parameters, usage variants, and practical advice. Missing output description but compensated by clear behavioral expectations. Adequate for agent 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%, baseline 3. Description adds value beyond schema by providing examples, defaults, and contextual advice (e.g., including portfolio_url for self-qualification). Adds nuance like discovery_offer only used in counter route.

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 declines spec work requests, with a specific verb and resource. It distinguishes from siblings like competitor_response_email, client_decline_email, and proposal_expiry_reminder_email by explaining each sibling's 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 explains when to use each route (decline vs counter) and differentiates from sibling tools by describing their specific use cases, providing clear guidance on tool selection.

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