Skip to main content
Glama

Briefdesign-Vorlagen auflisten

letter_design_list_presets
Read-only

Liefert die vom Inhaber freigegebenen native-v2 Briefpapiere als sichere Ausgangspunkte für Kündigung, Rechnung, Mahnung, Angebot, Vertrag und Behördenpost. Sie wächst mit jeder abgenommenen Vorlage. Die normale Liste nennt je Vorlage ID, Name, Beschreibung und Schlagwörter; mit presetId kommen das vollständige Design und genau eine echte Composer-Vorschau samt Inline-PNG. EN: Returns the owner-approved native-v2 letterheads as safe starting points for cancellations, invoices, payment reminders, quotes, contracts and letters to public authorities. It grows with every curated design that passes review. The plain list gives id, name, description and tags per preset; presetId returns the full design and exactly one real-composer preview with an inline PNG.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "letter_design_list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNo
presetIdNoOptional: lädt genau eine Vorlage samt gerenderter Vorschau. Ohne presetId bleibt die Liste bildfrei und günstig. EN: Optional: loads one preset with its rendered preview. Without presetId the list stays image-free and cheap.
reasoningNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / presetId / description
      Previous value: -"Optional: genau eine Vorlage samt gerenderter Vorschau laden. Ohne presetId bleibt die Liste bildfrei und günstig. EN: Optional: load one preset with its rendered preview. Without presetId the list stays image-free and cheap."New value: +"Optional: lädt genau eine Vorlage samt gerenderter Vorschau. Ohne presetId bleibt die Liste bildfrei und günstig. EN: Optional: loads one preset with its rendered preview. Without presetId the list stays image-free and cheap."
  2. Changed1 schema field changed
    • changedInput schema / properties / presetId / description
      Previous value: -"Optional: genau eine Vorlage samt gerenderter Vorschau laden. Ohne presetId bleibt die Liste bildfrei und guenstig. EN: Optional: load one preset with its rendered preview. Without presetId the list stays image-free and cheap."New value: +"Optional: genau eine Vorlage samt gerenderter Vorschau laden. Ohne presetId bleibt die Liste bildfrei und günstig. EN: Optional: load one preset with its rendered preview. Without presetId the list stays image-free and cheap."
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: only owner-approved (curated/reviewed) designs are returned, the list grows over time, and the payload cost differs sharply between the cheap image-free list and the presetId call that embeds exactly one inline PNG.

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 content is front-loaded and well ordered, with the mode distinction stated early. But the entire text is duplicated verbatim in German and English, roughly doubling length with zero added information, which works against conciseness for an agent paying per token.

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 read-only list tool with no output schema, the description does the necessary work of enumerating returned fields per item (id, name, description, tags) and describing what the presetId mode returns (full design plus one real-composer preview). Only the pagination/'pages' and 'resolution' semantics are left unexplained.

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 only 25%, so the description must carry more weight than it does. It explains presetId (which the schema already documents), but says nothing about what 'pages' (1-2) controls, why 'reasoning' exists, or what 'resolution' thumb vs. full actually changes — even though the preview image is the tool's most costly output.

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: it returns owner-approved native-v2 letterhead presets as starting points for named document categories, and explains the two modes (plain list vs. single presetId load). This is far clearer than the bare name, though it never contrasts itself with close siblings such as letter_design_list or letterhead_list, so an agent must infer which listing tool applies.

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?

Implied guidance exists: the plain call is described as an image-free, cheap discovery step, and presetId as the way to fetch one preset with a rendered preview. However, there is no explicit when-not advice and no named alternative among the many sibling listing/preview tools, so the routing decision is left to inference.

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.