Skip to main content
Glama

service_package_email

Draft a professional email offering fixed-price service packages (e.g., Starter, Growth, Scale) to a prospect. Clearly present each tier's name, inclusions, and price.

Instructions

Write a professional email presenting 2–3 productized service packages to a prospect. Used when you offer fixed-price, structured tiers rather than quoting per project — e.g. Starter / Growth / Scale, or Essential / Pro / Premium. Presents each tier with a clear name, what's included, and price. Distinct from rate_card_email (hourly/day rates sent when asked) and draft_proposal (responding to a specific brief). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prospect_nameYesFirst name of the prospect
service_typeYesWhat the packages are for (e.g. 'website design', 'monthly SEO', 'brand identity', 'content strategy')
package_1_nameYesName of the entry-level package (e.g. 'Starter', 'Essential', 'Foundation')
package_1_priceYesPrice of the entry package (e.g. '$800', '$500/month', 'from $1,200')
package_1_includesYesWhat is included in the entry package — comma-separated or short description (e.g. '3 pages, 1 revision round, delivered in 2 weeks')
package_2_nameNoOptional: name of the mid-tier package (e.g. 'Growth', 'Professional', 'Standard')
package_2_priceNoOptional: price of the mid-tier package
package_2_includesNoOptional: what is included in the mid-tier package
package_3_nameNoOptional: name of the premium package (e.g. 'Scale', 'Premium', 'Enterprise')
package_3_priceNoOptional: price of the premium package
package_3_includesNoOptional: what is included in the premium package
recommended_packageNoOptional: which package to highlight as the recommended choice — use the package name (e.g. 'Growth'). Omit to present all tiers neutrally.
pitch_contextNoOptional: one sentence connecting to the prospect's stated need or context (e.g. 'you mentioned you want to launch before Q3', 'based on our call, you need something that scales with your team'). Used to personalise the opening.
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 bears full burden. It adds useful behavioral context: 'Does not count against your monthly draft limit.' It also implies an email generation action but does not mention required permissions or 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.

Conciseness5/5

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

Three sentences with no wasted words. First sentence states purpose, second provides context, third distinguishes from siblings and adds draft limit info. Highly efficient.

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?

Tool has 14 parameters (many optional) and no output schema. Description covers when to use, what it produces, and distinguishes from alternatives. It adequately fills gaps given the rich input schema. Could mention the output is a full email body, but inferable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description does not add meaning beyond what the schema already provides for parameters. The schema itself describes each parameter sufficiently.

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 action ('Write a professional email'), resource ('productized service packages'), and scope ('2–3 packages, fixed-price structured tiers'). It distinguishes from siblings 'rate_card_email' and 'draft_proposal'.

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 states when to use ('when you offer fixed-price, structured tiers') and when not ('rather than quoting per project'). Names alternatives ('Distinct from rate_card_email... and draft_proposal').

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