Skip to main content
Glama

equity_or_deferred_payment_response

Generate a professional email response when a client offers equity, revenue share, or deferred payment instead of cash. Choose to decline politely, counter with conditions, or open discussion.

Instructions

Write a professional, considered response when a client proposes paying you in equity, exposure, revenue share, or deferred payment instead of (or alongside) a cash fee. The hardest part of this email is saying no without burning the relationship — or saying yes with the right conditions. Three modes: decline (default — polite, firm, no-door-slamming; explains your policy without moralising), counter (you're open to it under specific conditions — e.g. partial cash + equity, milestone-based deferred, or a minimum cash floor), and open_to_discuss (you'd like to hear more before committing either way — useful when the offer might be genuinely interesting but you need more information). Distinct from discount_request_response (which handles cash price negotiation). Does not count against your monthly draft limit. Required: client_name, proposal_type (e.g. 'equity stake', 'revenue share', 'deferred payment after launch', 'exposure and portfolio work'). Optional: response_mode (decline | counter | open_to_discuss), project_description, your_conditions (only used in counter mode — what would make you say yes, e.g. '50% cash upfront and 5% equity'), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or the name they used to sign off
proposal_typeYesWhat they're offering instead of cash (e.g. 'equity stake', 'revenue share', 'deferred payment after launch', 'exposure and a portfolio piece'). Used to keep the reply specific, not generic.
response_modeNodecline (default): polite, firm no — explains your policy, keeps the door open for paid work. counter: you'd say yes under specific conditions — state them clearly. open_to_discuss: you need more detail before deciding — ask the right questions.
project_descriptionNoOptional: brief description of the project (e.g. 'mobile app for their fintech startup'). Helps make the response feel specific.
your_conditionsNoOptional (counter mode only): what would make you say yes, stated plainly (e.g. '50% of the standard rate upfront and 5% equity', 'full fee deferred 90 days with a signed agreement', 'minimum $2k retainer plus revenue share above $10k monthly'). Auto-formatted into the email.
your_nameNoYour name for the sign-off
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that the tool generates an email, has three modes with a default, and that certain parameters are mode-specific. It also notes it does not count against a monthly draft limit. Behavioral traits are well-covered, though it doesn't explicitly state it's a non-destructive read operation.

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 fairly concise and front-loaded with the main purpose. Each sentence adds value, covering modes, usage, and parameter guidance. Minor redundancy (e.g., 'the hardest part...') could be trimmed, but overall it is well-structured and informative.

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 (three modes, six parameters, no output schema), the description covers the essential aspects: required/optional parameters, mode behavior, parameter conditions, and differentiation from sibling. It doesn't explicitly describe the output format, but given no output schema, this is acceptable.

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%, so baseline is 3. The description adds value by explaining usage context for each parameter (e.g., your_conditions used only in counter mode), clarifying the default for response_mode, and providing practical examples. This goes beyond the schema's basic descriptions.

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 response to non-cash payment proposals. It specifies the verb (write a response), resource (equity, deferred payment, etc.), and distinguishes from the sibling tool discount_request_response, making it easy for the agent to select correctly.

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 explicitly differentiates from discount_request_response and explains the three response modes (decline, counter, open_to_discuss) with clear guidance on when to use each. It could also mention when not to use the tool, but the distinction from the sibling provides adequate 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