Skip to main content
Glama

TrueInterview

Write a cover letter for a job

write_cover_letter

Write the candidate's cover letter for one job with TrueInterview's cover-letter writer, grounded in their résumé and the posting, checked for invented facts and stock phrases. Give exactly one of job_id, application_id, or job_description with company and role; instruction is the candidate's own steer ("mention my Kafka migration"). It uses the candidate's monthly writing allowance. Show the candidate the letter before it goes anywhere.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "write_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
job_idNo
companyNo
instructionNo
application_idNo
job_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-destructive, non-idempotent), the description discloses two behaviors an agent could not otherwise know: the call consumes the candidate's monthly writing allowance, and the output is grounded in the résumé and posting and screened for invented facts and stock phrases. "Show the candidate the letter before it goes anywhere" also clarifies that nothing is sent externally, which is meaningful for a write tool.

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 core action and its grounding are front-loaded, followed by input constraints and side effects in a logical order, with no filler sentences. It is dense but every clause adds information, though the long compound opening sentence takes effort to parse.

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?

With no output schema and no annotations about quota or side effects, the description supplies the missing context: quota consumption, grounding sources, quality checks, and the expectation of showing the draft before any external use. It does not describe return shape or error behavior, but the essential call-time context is present.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: it explains the mutually exclusive input modes among job_id, application_id, and job_description, the company/role pairing that accompanies raw job descriptions, and the meaning of instruction with a concrete example. No parameter meaning is left purely to field names.

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 a precise verb and resource: "Write the candidate's cover letter for one job," and adds grounding and fact-checking behavior. It does not explicitly distinguish itself from the sibling generate_application_documents, which plausibly also produces application documents, so the differentiation gap keeps it off a 5.

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

Usage Guidelines4/5

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

It gives a concrete input rule ("Give exactly one of job_id, application_id, or job_description with company and role") and explains what instruction is for, with a worked example. It stops short of naming when to choose this tool over a document-generation sibling or when not to use it at all.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources