Skip to main content
Glama

Delete a cover letter

deleteCoverLetter
DestructiveIdempotent

Delete one saved cover letter for good (letterId from listCoverLetters). A copy already attached to a tracked application stays there. Confirm with the candidate 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": "deleteCoverLetter"
  }
}

Input Schema

NameRequiredDescriptionDefault
letterIdYes

Output Schema

NameRequiredDescriptionDefault
letterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds two things they cannot convey: deletion is permanent ("for good") and a copy already attached to a tracked application survives the delete. It also discloses that inputs and results are logged, which is a real operational fact an agent should know before mutating data.

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?

Three short, front-loaded sentences: the destructive effect and the attached-copy caveat come first, then the confirmation step, then the logging notice. The privacy sentence is generic boilerplate but is short and clearly separable from the operational guidance.

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

Completeness5/5

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

With only one required parameter, rich annotations, and an output schema that covers return values, the remaining burden is exactly what is provided: permanence, side effects on attached copies, an ID source, and a confirmation prerequisite. Nothing an agent needs to call this safely is missing.

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?

Schema description coverage is 0%, so the schema gives only type/format/pattern with no meaning. The description compensates by naming the argument and its source system (letterId from listCoverLetters), which is the one semantic detail an agent needs to supply a valid value.

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?

The description pairs a specific verb ("Delete") with a specific resource ("one saved cover letter") and scopes it to a single item by letterId. The resource name alone distinguishes it from siblings such as deleteApplication, deleteResume, and deleteTailoredResume.

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?

It states a clear precondition ("Confirm with the candidate before calling") and tells the agent where the identifier comes from (listCoverLetters). It stops short of naming an alternative or an explicit when-not-to-use case, which keeps it below 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