camelotwebtools-mcp

camelot_cold_outreach_emailer

Idempotent

Create personalized cold sales outreach emails and follow-up sequences that address a prospect's specific pain point and present a tailored solution.

Instructions

Cold Outreach Emailer: Craft personalized cold sales outreach email templates and follow-up sequences.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/cold-outreach-emailer

Input Schema

TableJSON Schema

Name	Required	Description	Default
`painPoint`	No	Target customer frustration or pain point addressed	Overpaying for 10 disconnected document and conversion SaaS subscriptions
`prospectName`	No	Prospective client or recipient contact name	Alex
`solutionPitch`	No	Compelling product pitch and solution summary	Consolidate 79 client work, finance, and developer tools under one lifetime license
`prospectCompany`	No	Target prospective customer organization	Acme Media Group

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Execution status of the tool (success or error)
`prefillUrl`	Yes	Direct deep-link URL to view, edit, and export in Camelot Web Tools
`canonicalUrl`	Yes	Canonical web URL for this tool on camelotwebtools.com
`documentTitle`	Yes	Title of the generated document, report, or calculation output
`documentMarkdown`	Yes	Complete structured output and body formatted in clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations indicate idempotentHint=true, so the tool is safe to repeat. The description adds context by mentioning 'Local browser processing' and provides a canonical URL, which is useful. However, it doesn't disclose what the output format is or any limitations, but with annotations covering idempotency, this is adequate. No contradiction with annotations.

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 concise at two sentences, with the core purpose front-loaded. The extra details about local processing and canonical URL are brief and not redundant. No filler.

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?

Given the tool has an output schema (not shown in detail but present), the description doesn't need to explain return values. The input parameters are well-defined in the schema. However, it could benefit from specifying how the tool handles personalization or whether it generates sequences solely, but for a template generator this is sufficient.

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 coverage is 100%, so all parameters have descriptions. The description does not add significant extra meaning beyond the schema, but it does align with the tool's purpose. The defaults are already informative, so a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: crafting personalized cold sales outreach email templates and follow-up sequences. It specifies the resource (cold outreach emails) and the action (create/craft). While it doesn't explicitly differentiate from siblings like camelot_email_campaign_writer or camelot_ad_copy_template_builder, the purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (for cold outreach emails and follow-ups) but does not explicitly state when to use this tool versus alternatives like camelot_email_campaign_writer. It lacks clear exclusions or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server