Skip to main content
Glama
JesusCabreraReveles

honest-cv

by JesusCabreraReveles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

build_letter

Render an approved cover letter to a one-page PDF and/or DOCX with ATS checks; it validates claims, refuses on issues, and returns files and warnings.

Instructions

Render an approved cover letter to a one-page PDF and/or DOCX with the CV's ATS checks. Use it after drafting the letter with the person and running check_claims; for the CV itself use build_cv. It runs check_claims again and refuses while there are problems. Returns the files and any warnings to show the person.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage of the output: en (English) or es (Spanish).en
roleYesJob title, as in the job post.
closingNoClosing line. Default: Sincerely, / Atentamente,
companyYesCompany name, as in the job post.
formatsNoFormats to write: pdf, docx or both. Default: both.
out_dirNoOutput folder. Default: <profile>/out.
profileNoPath of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE).
greetingNoOpening line. Default: Dear Hiring Team, / Estimado equipo de selección:
keywordsNoKeywords of the job post, for check_claims.
recipientNoHiring manager or team, if the post names one.
paragraphsYesThe body, one string per paragraph, approved by the person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.2
    • changedInput schema / properties / closing / description
      Previous value: -"Default: Sincerely, / Atentamente,"New value: +"Closing line. Default: Sincerely, / Atentamente,"
    • changedInput schema / properties / formats / description
      Previous value: -"Default: both."New value: +"Formats to write: pdf, docx or both. Default: both."
    • changedInput schema / properties / greeting / description
      Previous value: -"Default: Dear Hiring Team, / Estimado equipo de selección:"New value: +"Opening line. Default: Dear Hiring Team, / Estimado equipo de selección:"
    • changedInput schema / properties / lang / description
      Previous value: -"Language of the CV: en or es."New value: +"Language of the output: en (English) or es (Spanish)."
    • changedInput schema / properties / profile / description
      Previous value: -"Profile folder. Defaults to HONEST_CV_PROFILE."New value: +"Path of the profile folder. Leave it out to use the server's default (--profile or HONEST_CV_PROFILE)."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses a real behavioral trait beyond the annotations: the tool re-runs check_claims and refuses while problems exist, and returns files and warnings to show the person. Annotations only cover the safety profile (readOnly=false, destructive=false), which the description is consistent with, so the validation gate and return shape are genuine added value.

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 tight sentences, front-loaded with what it renders and immediately followed by prerequisites, the sibling alternative, and the guard behavior. Every clause carries information with no repetition of name or title.

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

Completeness5/5

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

No output schema exists, yet the description explains what is returned (files and warnings). Combined with 100% schema coverage on 11 parameters and the stated prerequisite chain, an agent has everything needed to invoke it 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?

Schema description coverage is 100%, so the 11 parameters are already fully documented in the schema. The description adds only tangential mapping ('with the CV's ATS checks' relating to keywords) and no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (render) and resource (approved cover letter) plus output formats (one-page PDF and/or DOCX), and explicitly names the sibling it is not (build_cv) for the CV itself. An agent can distinguish this from build_cv without opening either schema.

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?

Gives explicit sequencing preconditions ('after drafting the letter with the person and running check_claims') and routes to the alternative ('for the CV itself use build_cv'). The when-to-use and the sibling boundary are both stated outright.

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

Deploy Server

Other Tools