Skip to main content
Glama

delete_cover_letter

Destructive

Delete one cover letter by id. This cannot be undone.

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": {
      "coverLetterId": "<coverLetterId>"
    },
    "name": "delete_cover_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
coverLetterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the important caveat that the deletion "cannot be undone," reinforcing permanence, but it says nothing about behavior when the id does not exist, whether related data is affected, or what the response contains.

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?

Two short sentences with no waste, and the action plus scope is front-loaded before the irreversibility warning. Nothing could be removed without losing information.

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 one-parameter destructive tool whose annotations already flag destructiveness and closed-world scope, the definition covers what is needed: target, identifier and permanence. The only real gap is error/nonexistent-id behavior, which is minor at this complexity.

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?

The schema has zero description coverage on the single required parameter coverLetterId, so the description must carry the load. "By id" clarifies that the string is the cover letter's identifier, which is modest but real added meaning; it does not state the id format or where to obtain one.

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 ("Delete one cover letter") and bounds scope to a single record via "by id." It is clearly distinguishable from create_cover_letter, get_cover_letter and update_cover_letter by its verb, though it never names or contrasts a sibling explicitly.

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 implied: you call it with a cover letter id when you want that entry removed. There is no explicit when-to-use versus when-not-to-use guidance, no mention of alternatives such as update_cover_letter as a non-destructive path, and no stated prerequisites (e.g. ownership or permissions).

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