Skip to main content
Glama

Check text and save the cover letter

freeapply_check_text
Idempotent

Checks cover letters and free-text answers against your résumé and saved facts, flags unsupported claims, and saves passing cover letters as PDFs for job applications.

Instructions

Checks a cover letter or free-text answer against what the user really has; saves a passing cover letter as a PDF to upload. Every piece of prose is checked here before you type or attach it (freeapply_update_job only records). Use: before typing any written answer or attaching any letter, and after each fix. Not for short fields straight from settings (name, date, yes/no). Behavior: flags every skill, tool, number or claim the résumé, settings, highlights and saved answers don't support. Without save, changes nothing. With save, a passing letter becomes a PDF in the documents folder, kept with the job; a failing one is never saved; saving again replaces the file; refused once the job is applied. Until setup has stored the résumé's text, most claims are reported unsupported. Returns: {ok, problems} (plain sentences: fix, remove or ask the user). With job_id also keywords {used, unused}: the posting's supported skills this text uses / could still use. With save also file {path, name, bytes}, or note (why not saved). Errors: save without kind cover_letter and job_id; unknown job_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "freeapply_check_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNocover_letter: also checks the user's length, sign-off, leftover placeholders and that the company is named. answer (default): facts only.
saveNoSave a passing cover letter as a PDF (default false). For a letter, pass it from the first call: checked and saved at once.
textYesThe letter or answer, exactly as you will type or attach it.
job_idNoAdds the posting's keywords; numbers from the job's posting, title, pay, location and posting id, and the user's answers for this job, count as facts. Needed for save.
companyNoThe employer, when there is no job_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.4
    • changedInput schema / properties / company / description
      Previous value: -"The employer, when there is no job_id. Optional."New value: +"The employer, when there is no job_id."
    • changedInput schema / properties / job_id / description
      Previous value: -"The job it is for. Optional; needed for save."New value: +"Adds the posting's keywords; numbers from the job's posting, title, pay, location and posting id, and the user's answers for this job, count as facts. Needed for save."
    • changedInput schema / properties / kind / description
      Previous value: -"What the text is. Optional; default answer."New value: +"cover_letter: also checks the user's length, sign-off, leftover placeholders and that the company is named. answer (default): facts only."
    • changedInput schema / properties / save / description
      Previous value: -"Save a passing cover letter as a PDF. Optional; default false."New value: +"Save a passing cover letter as a PDF (default false). For a letter, pass it from the first call: checked and saved at once."
    • changedInput schema / properties / text / description
      Previous value: -"The cover letter or answer to check, exactly as you will type or attach it."New value: +"The letter or answer, exactly as you will type or attach it."
  2. Changed4 schema fields changedv1.0.2
    • changedInput schema / properties / company / description
      Previous value: -"The employer it is addressed to. Optional; a cover letter that never mentions it is flagged."New value: +"The employer, when there is no job_id. Optional."
    • changedInput schema / properties / job_id / description
      Previous value: -"The job it is for. Optional; numbers from its posting and the user's answers for it then count as supported."New value: +"The job it is for. Optional; needed for save."
    • addedInput schema / properties / save
      Added value: +{
      +  "description": "Save a passing cover letter as a PDF. Optional; default false.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / text / description
      Previous value: -"The cover letter or answer to check."New value: +"The cover letter or answer to check, exactly as you will type or attach it."
  3. Changed6 schema fields changedv1.0.1
    • addedInput schema / properties / company / description
      Added value: +"The employer it is addressed to. Optional; a cover letter that never mentions it is flagged."
    • addedInput schema / properties / job_id / description
      Added value: +"The job it is for. Optional; numbers from its posting and the user's answers for it then count as supported."
    • addedInput schema / properties / job_id / minimum
      Added value: +1
    • addedInput schema / properties / kind / description
      Added value: +"What the text is. Optional; default answer."
    • addedInput schema / properties / kind / enum
      Added value: +[
      +  "cover_letter",
      +  "answer"
      +]
    • addedInput schema / properties / text / description
      Added value: +"The cover letter or answer to check."
  4. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond annotations: explains that without save nothing changes, a passing letter becomes a PDF kept with the job, a failing letter is never saved, saving again replaces the file, saving is refused once the job is applied, and claims are mostly unsupported until setup has stored the résumé text. It also names the specific checks (skills, tools, numbers, claims) and the error conditions.

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?

Well structured with labeled Use, Behavior, Returns and Errors sections. Despite being long, every section front-loads the decision-relevant information and no sentence is wasted.

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?

With no output schema, the description fully compensates by documenting the return shape ({ok, problems}, keywords, file, note) and the error cases. Combined with the detailed usage and behavior sections, an agent has everything needed to call this correctly.

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 the baseline is 3. The description still adds useful cross-parameter constraints: save requires kind cover_letter and job_id, company is the fallback when job_id is absent, and job_id activates keyword analysis and treats posting facts as supported.

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 and resource: checks a cover letter or free-text answer against the user's real facts and optionally saves a passing cover letter as a PDF. It explicitly distinguishes itself from freeapply_update_job ('only records') and from short settings-derived fields, so an agent can route correctly without opening the 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?

Provides explicit timing ('before typing any written answer or attaching any letter, and after each fix') and explicit exclusions ('Not for short fields straight from settings (name, date, yes/no)'), plus names the sibling that only records. No inference required.

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