Skip to main content
Glama

Edit a cover letter

editCoverLetter
DestructiveIdempotent

Replace the wording of one saved cover letter (letterId from listCoverLetters) with the full new letter: greeting, paragraphs, closing and signature, plus its name. Clera re-renders the PDF. Read the letter first, change only what the candidate asked for, show them the result and get a yes before calling.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "letterId": "<letterId>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "editCoverLetter"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentYes
letterIdYes

Output Schema

NameRequiredDescriptionDefault
letterYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the crucial semantics that this is a full replacement rather than a patch (unmentioned fields are lost) and that Clera re-renders the PDF as a side effect. It also discloses that inputs and results are recorded for usage tracking and support, which annotations do not cover.

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 replacement semantics, then the side effect, then the workflow, then the required disclosure. Every sentence carries information; only the data-recording notice is boilerplate, and it is short.

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?

For a destructive, nested-payload mutation, the description covers what is replaced, how to obtain the id, the confirmation workflow, and the PDF side effect, and an output schema exists so return values need not be explained. The remaining gap is the content-field constraints, which neither the schema prose nor the description surfaces.

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

Parameters3/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 it does partially by spelling out the nested content fields and tracing letterId to listCoverLetters. It adds nothing about constraints the agent would otherwise miss, such as the 1-6 paragraph limit or the character caps, so the compensation is incomplete.

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: replace the wording of one saved cover letter, keyed by letterId, and enumerates the content it carries (greeting, paragraphs, closing, signature, name). It also points at listCoverLetters as the source of the id, which cleanly separates it from generateCoverLetter and deleteCoverLetter.

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?

Gives concrete preconditions and a workflow: read the letter first, change only what the candidate asked for, show the result and get a yes before calling. That is strong when-to-use guidance, though it never names an alternative tool (e.g., generate vs. edit) or a when-not-to-use condition.

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