Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Vorlagen auflisten

template_list
Read-only

Vorlagen auflisten, Template-Liste, template list: Listet die verfügbaren Brief-Vorlagen für Anlässe wie Kündigung, Rechnung, Mahnung, Angebot, Vertrag und Behördenpost, mit Kategorie, Version und ihren Platzhaltern (Merge-Feldern). Der exakte technische Tool-Name ist template_list; falls dein Client Tools verzögert lädt, suche nach template_list. Standardmäßig nur freigegebene Vorlagen; mit statusFilter und dem Scope template:write auch offene Entwürfe. Jeder Eintrag sagt mit curated: true, ob es eine kuratierte FrankKi-Standardvorlage ist (die Bibliothek zum Kopieren), und mit hasBlocks: true, ob sie ein strukturiertes Layout mit Tabellen und Summen trägt statt Fließtext. Nächster Schritt: template_get liefert eine Vorlage vollständig (bei einer Blockvorlage inklusive blocksTemplate und styleDefs zum Kopieren und Anpassen), template_apply_with_merge_fields füllt sie mit deinen Werten. EN: List templates, template list: lists the available letter templates for occasions such as cancellation, invoice, payment reminder, quote, contract and letters to public authorities, with category, version and their placeholders (merge fields). The exact technical tool name is template_list; if your client defers tools, search for template_list. By default it returns released templates; with statusFilter and the template:write scope also open drafts. Every entry says with curated: true whether it is a curated FrankKi standard template (the library to copy from), and with hasBlocks: true whether it carries a structured layout with tables and totals instead of plain text. Next step: template_get returns one template in full (for a block template including blocksTemplate and styleDefs to copy and modify), template_apply_with_merge_fields fills it with your values.

Input Schema

NameRequiredDescriptionDefault
limitNoStandard 50, maximal 100. EN: Default 50, maximum 100.
queryNoSuchwort für Name und Kategorie, z. B. Mahnung oder Miete. EN: Search word for name and category, e.g. Mahnung or Miete.
offsetNoVersatz für die Seitennavigation. Standard 0. EN: Offset for pagination. Default 0.
reasoningNo
statusFilterNoreleased (Standard) zeigt alle freigegebenen Vorlagen. Eigenständige Formularvorlagen tragen sendable:false und brauchen beim Anwenden ein Anschreiben. draft zeigt nur offene Entwürfe, all beide. draft und all brauchen zusätzlich den Scope template:write. EN: released (default) shows every released template. Standalone form templates carry sendable:false and require a cover letter when applied. draft shows only open drafts, all shows both. draft and all additionally require the template:write scope.released
kategorieFilterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Standard 20, maximal 100. EN: Default 20, maximum 100."New value: +"Standard 50, maximal 100. EN: Default 50, maximum 100."
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Suchwort für Name und Kategorie, z. B. Mahnung oder Miete. EN: Search word for name and category, e.g. Mahnung or Miete.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint=false, so the description does not need to re-establish safety; instead it adds real value: scope requirements for drafts, the meaning of curated and hasBlocks flags, and the sendable:false caveat for form templates. It stops short of describing pagination behaviour or ordering, hence 4 rather than 5.

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 is front-loaded and the scoping sentence comes early, but the entire description is duplicated verbatim in English, roughly doubling length with zero added information. Useful content is padded by repetition and by client-plumbing hints ('falls dein Client Tools verzögert lädt').

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?

There is no output schema, and the description does a good job covering the return shape (category, version, placeholders/merge fields, curated, hasBlocks). Given six parameters with no required fields, only kategorieFilter and pagination remain unaddressed, which is a minor gap.

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?

statusFilter is well explained in the description and matches the schema, and the query/kategorieFilter concepts are hinted at via the category/'Suchwort' wording. But kategorieFilter has no description at all and limit/offset are only covered by the schema; with 67% coverage the description neither fully compensates nor adds much beyond the schema.

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 ('Listet die verfügbaren Brief-Vorlagen') plus the domains it covers (Kündigung, Rechnung, Mahnung…), and clearly separates it from template_get which returns a single template in full. An agent can distinguish it from letter_list, document_list and letter_design_list from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the default behaviour (released only), the alternative (draft/all via statusFilter plus template:write scope), and routes to the two follow-up tools with their purposes. This is when/when-not plus named alternatives, not inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FrankKi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources