Skip to main content
Glama

Briefdesign löschen

letter_design_delete
Destructive

Archiviert (löscht) ein gespeichertes Briefpapier (Briefdesign). Neue Sendungen laufen danach über die verbleibenden Briefpapiere, egal ob Kündigung, Rechnung, Mahnung, Angebot, Vertrag oder Behördenpost; bereits versendete Briefe behalten ihr Original zur Nachvollziehbarkeit. EN: Archives (deletes) a saved letterhead (letter design). New sends then run on the remaining letterheads, whether cancellation, invoice, payment reminder, quote, contract or letter to a public authority; already-sent letters keep their original for auditability.

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": {
      "designId": "<designId>"
    },
    "name": "letter_design_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
designIdYesDas zu löschende Briefdesign. EN: The letter design to delete.
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / designId / description
      Previous value: -"Das zu loeschende Briefdesign. EN: The letter design to delete."New value: +"Das zu löschende Briefdesign. EN: The letter design to delete."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations flag destructiveHint=true, and the description adds genuinely useful context beyond them: the operation is an archive/soft-delete, already-sent letters retain their originals for auditability, and future sends fall back to remaining letterheads. This tells the agent the blast radius and reversibility posture.

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

Conciseness3/5

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

The core consequence (archive, sent letters preserved) is front-loaded, but the full text is duplicated in German and English and padded with an enumeration of letter types (Kündigung, Rechnung, Mahnung…) that adds no decision-relevant 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 destructive tool with no output schema, the description covers the key behavioral consequences an agent needs (archival semantics, effect on future sends, auditability of past letters). The main gap is the unexplained 'reasoning' parameter.

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 coverage is 50%: designId is documented in the schema and the description only restates it, while the 'reasoning' parameter is undocumented in both places. The description does not compensate for the uncovered parameter, so it adds little beyond the schema here.

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?

States a specific verb and resource ('Archiviert (löscht) ein gespeichertes Briefpapier') and clarifies that it is a soft-archive rather than a hard purge, which distinguishes it from siblings like letter_design_save or letter_design_list. It does not explicitly name a sibling, but the operation is unambiguous.

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?

The description implies when this is used (removing a letterhead so new sends fall back to remaining ones), but gives no explicit when-not guidance, preconditions, or named alternative tools. An agent can infer the usage scene but must reason it out.

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.