Skip to main content
Glama

create_cover_letter

Create a blank cover letter from the profile header. Header links are LinkedIn, then the live Linkdfolio website (unless preferences.siteLinkInDocuments is false), then the profile links. Does not call a model. Returns the letter, its version, and an appUrl.

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": "create_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
templateIdNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not open-world), and the description adds real context beyond them: 'Does not call a model' tells the agent this is cheap/deterministic, and it discloses return contents (letter, version, appUrl) despite there being no output schema. The header-link ordering rule and the preferences.siteLinkInDocuments condition further describe what the produced document will contain.

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 the action and resource, then behavior, then return value – a sensible order with no filler. The header-link ordering clause is the longest part and is slightly disproportionate for a secondary concern, but it still carries concrete information.

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?

For a simple two-optional-parameter creation tool with no output schema, the description covers the return shape, model behavior, and document composition, which is most of what is needed. The remaining gap is parameter meaning: an agent cannot tell from the description what title or templateId do, or which template applies by default.

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% for two parameters (title, templateId), and both are optional, yet the description never mentions either one. It spends its detail budget on header link ordering instead of explaining what title or templateId change about the created letter, leaving the agent to guess from the property names alone.

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 gives a specific verb and resource ('Create a blank cover letter from the profile header') and the word 'blank' implicitly distinguishes it from the sibling duplicate_cover_letter. It does not explicitly name that sibling, so an agent must infer the distinction rather than being routed to it.

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

Usage Guidelines3/5

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

Usage is only implied by 'blank' and 'from the profile header' – there is no statement of when to prefer this over duplicate_cover_letter or create_resume. No prerequisites or exclusions are stated, so the agent must reason from the sibling names themselves.

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