Skip to main content
Glama

TrueInterview

Tailor résumé and write cover letter in one call

generate_application_documents

Generate both the tailored résumé and the cover letter for one job in a single call, so an agent applying to a role gets both documents in one round trip. Give exactly one of job_id, application_id, or job_description with company and role (job pages are not fetched here). Returns the tailored résumé with its changes and PDF link, and the cover letter, each with its quality check and the writing allowance after both. It uses the candidate's monthly writing allowance for both. When one fails, the other still comes back and errors names the one that failed. Show the candidate both before they go 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": "generate_application_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
job_idNo
companyNo
keywordsNoTerms from the posting the candidate wants on the résumé.
intensityNokeywords: only surface the posting terms; rewrite (default): reword bullets toward the role.
instructionNoThe candidate's steer for the cover letter.
application_idNo
job_descriptionNo
include_resume_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing quota consumption ('uses the candidate's monthly writing allowance for both'), partial-failure semantics ('when one fails, the other still comes back and errors names the one that failed'), and the fact that job pages are not fetched. These are exactly the operational traits an agent needs and none are derivable from the annotation flags.

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?

Front-loaded with purpose, then selection rules, then return shape, then failure behavior — a sensible order with no filler. There is minor redundancy between 'the writing allowance after both' and 'It uses the candidate's monthly writing allowance for both', which could be merged.

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?

No output schema exists, but the description compensates by describing both return payloads, their quality checks, and the remaining allowance. For a 9-parameter, two-output composite tool the coverage is solid; the undocumented optional parameters (include_resume_file in particular) are the only meaningful omission.

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?

With only 33% schema description coverage, the description carries real weight: it states the exactly-one-of constraint across job_id, application_id, and job_description (a rule absent from the schema, which has no oneOf), and clarifies that company/role accompany a raw job_description since pages aren't fetched. It leaves keywords, intensity, instruction, and include_resume_file entirely to the schema, which is the remaining gap.

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 two concrete resources ('Generate both the tailored résumé and the cover letter for one job in a single call') and makes the aggregation value explicit ('both documents in one round trip'), which distinguishes it from the single-purpose siblings write_cover_letter and tailor_resume without naming them.

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?

The framing 'an agent applying to a role gets both documents in one round trip' makes the use case clear, and 'Show the candidate both before they go anywhere' adds post-call handling guidance. It stops short of explicit exclusions (e.g. 'if you only need the résumé, use tailor_resume'), so a 4 rather than a 5.

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