Skip to main content
Glama

duplicate_cover_letter

Copy one cover letter to a new id, such as a separate letter for another posting. The source is not changed. To change an existing letter, use update_cover_letter. Returns the new letter, its version, and an appUrl.

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": {
      "fromCoverLetterId": "<fromCoverLetterId>"
    },
    "name": "duplicate_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
fromCoverLetterIdYes

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 readOnlyHint=false and destructiveHint=false; the description adds meaningful context beyond them by stating 'The source is not changed' and naming what comes back (new letter, its version, and an appUrl). It does not mention permission requirements or whether the copy inherits fields not overridden, but the core behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the operation, followed by the non-mutation guarantee, the sibling alternative, and the return shape. No filler or redundancy.

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, the description helpfully names the return payload, and the mutation semantics are covered alongside the annotations. The only real gap is the undocumented 'title' parameter, which matters for a two-parameter tool.

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. It implies fromCoverLetterId via 'The source', but the optional 'title' parameter is never mentioned, leaving its purpose (presumably the new letter's title) to inference.

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 ('Copy one cover letter to a new id') plus the intent ('a separate letter for another posting'), which is enough for an agent to distinguish it from create_cover_letter and update_cover_letter without opening any schema.

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?

Explicitly routes modification requests to update_cover_letter, giving a clear when-not-to-use condition. It stops short of contrasting duplication with create_cover_letter (writing a letter from scratch), so the alternative space is only partially covered.

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