camelotwebtools-mcp

camelot_cover_letter_writer

Idempotent

Draft a tailored cover letter using your experience, target role, company, and candidate details. Produce role-specific content that aligns your skills with the employer's needs.

Instructions

Cover Letter Writer: Draft a tailored cover letter from your experience and the role details you provide.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/cover-letter-writer

Input Schema

TableJSON Schema

Name	Required	Description	Default
`targetRole`	No	Target job position or executive level	Staff Infrastructure Engineer
`candidateName`	No	Full name of candidate or hire	Alex Morgan
`targetCompany`	No	Target prospective employer or client organization	Stripe
`coreExperience`	No	Core domain expertise and technical skills	Architected high-throughput payment settlement pipelines processing 50M+ daily events.

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

A3.6/5.0

Behavior4/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds the meaningful behavioral context 'Local browser processing,' which clarifies that no server-side processing occurs. This is a useful privacy/execution trait that goes beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loaded, but it includes a repetitive tool-name prefix 'Cover Letter Writer:' and a canonical URL that does little to help an agent invoke the tool. A minor punctuation typo ('provide..') also prevents it from being polished.

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 rich input schema, full parameter descriptions, and presence of an output schema, the description supplies the key remaining context: the tool's purpose and local browser processing. It is sufficiently complete for an agent to select and call this tool correctly.

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?

The schema description coverage is 100%, so the parameters are already well documented. The description's phrase 'from your experience and the role details you provide' generally aligns with the coreExperience and targetRole fields but does not add meaningful new semantics beyond the schema.

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 opens with 'Draft a tailored cover letter,' which is a specific verb and resource, and it directly ties the tool to the candidate's experience and role details. It is not a tautology and is clearly distinguishable from unrelated siblings, though it does not explicitly contrast with closely-related tools like resume_builder.

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 the intended use case: when a user needs a tailored cover letter from experience and role details. However, it provides no explicit when-not-to-use guidance or alternative routing among sibling document-generation tools, so usage context is reasonable but not fully developed.

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

Deploy Server