Skip to main content
Glama

project_inquiry_response_email

Craft a professional reply to a client's project inquiry, with options to ask qualifying questions or propose a discovery call directly. Structure the first email to move the conversation forward with specific details.

Instructions

Write the professional reply to an inbound project inquiry from a potential client — the email you send when someone reaches out asking if you're available for work. This is the first email in the client relationship, so tone and structure matter: warm enough to keep them engaged, professional enough to signal expertise, and specific enough to move toward a conversation. Two modes: reply_and_qualify (default — acknowledges the enquiry, asks 1-3 targeted qualifying questions to understand scope/budget/timeline before agreeing to a call, and proposes a next step) and reply_and_book (skip the qualifying questions and go straight to proposing a discovery call — use when the enquiry already includes enough detail). Distinct from cold_pitch (you reach out first), client_followup (chasing a silent prospect), and discovery_call_follow_up_email (sent after the call). Required: client_name, enquiry_summary (a brief description of what they're asking for, e.g. 'website redesign for a law firm' or 'monthly content for their SaaS product'). Optional: qualifying_questions (up to 3 questions you want answered before the call — auto-formatted as a bulleted list), response_mode (reply_and_qualify | reply_and_book), call_scheduling_link (Calendly or equivalent URL for one-click booking), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name or the name they used to sign off
enquiry_summaryYesBrief description of what they're asking for (e.g. 'website redesign for a law firm', 'monthly SEO content for their B2B SaaS product'). Used to make the reply feel specific, not templated.
qualifying_questionsNoOptional: up to 3 qualifying questions you want answered before agreeing to a call, comma-separated (e.g. 'What's your rough budget?, When do you need this live?, Do you have existing branding?'). Only used in reply_and_qualify mode.
response_modeNoreply_and_qualify (default): acknowledge + ask qualifying questions + propose next step. reply_and_book: skip questions, go straight to a discovery call — use when the enquiry already contains enough detail.
call_scheduling_linkNoOptional: Calendly or equivalent link for one-click call booking. Turns the next-step CTA into a direct link rather than a back-and-forth availability exchange.
your_nameNoYour name for the sign-off
Behavior3/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 tone requirements and the 'does not count against monthly draft limit' behavior, but it does not clarify what the tool actually outputs (e.g., returns email text, drafts, or sends) or what side effects occur. This missing information leaves ambiguity about tool behavior.

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 relatively long but well-structured: purpose first, then tone guidance, modes, sibling distinction, and parameters. Every sentence adds value, but it could be slightly more concise without losing information.

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

Completeness3/5

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

The description covers what the tool does and how to use it, but it fails to explain what the tool returns or the side effects (e.g., sending vs. generating text). Given no output schema, this is a notable gap. It omits error conditions or authorization needs, which are less critical but still relevant for a tool with 6 parameters.

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 meaningful context beyond schema descriptions: e.g., for 'enquiry_summary' it provides examples, for 'qualifying_questions' it explains format and usage, and for 'response_mode' it clarifies decision logic. This extra context improves parameter understanding.

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 reply to an inbound project inquiry. It specifies the verb ('write'), resource ('professional reply'), and context ('inbound project inquiry from a potential client'). It also distinguishes from siblings by naming specific alternative tools (cold_pitch, client_followup, discovery_call_follow_up_email).

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 explicitly states when to use the tool: 'the email you send when someone reaches out asking if you're available for work.' It provides two modes (reply_and_qualify and reply_and_book) with explicit guidance on when to use each, and it excludes scenarios covered by sibling tools via the 'Distinct from' clause.

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