Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Draft cover letter

generate_cover_letter
Read-onlyIdempotent

Generate a truthful job-specific cover letter for review.

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": {
      "jobId": "<jobId>"
    },
    "name": "generate_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNo
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered by structured data. Beyond that, the description adds real value with "truthful" (an anti-fabrication constraint on the generated content) and "for review" (the output is a draft a human must check). It still omits what source material grounds the letter — profile, CV, or job posting — and how long the result is.

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?

A single well-formed sentence with the purpose front-loaded and no filler. It is efficient, though its brevity is partly the cause of the missing parameter and usage guidance rather than a virtue in itself.

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

Completeness3/5

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

With no output schema and only 0% schema description coverage, the description should do more: it should say the tool returns letter text (inferable from "for review"), what the tone parameter accepts, and which stored data the letter draws on. As written it is minimally sufficient for a two-parameter generation tool but leaves the agent to guess on tone and grounding.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely does not. "Job-specific" loosely maps to the required jobId, but the `tone` parameter — an unconstrained free-form string with no enum — is never mentioned, so an agent has no idea what values are expected or what the default behavior is.

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?

"Generate a truthful job-specific cover letter" gives a specific verb (generate) and resource (cover letter) with a scoping qualifier (job-specific), which is enough to distinguish it from generic profile/resume builders like build_or_refine_resume. It does not explicitly name a sibling such as prepare_complete_application, so an agent cannot tell whether the latter already bundles a cover letter.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, and no prerequisites (that a job be saved or analyzed first, or that a profile exist). The phrase "for review" hints that the output is a draft, but that is an output trait, not usage guidance.

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.