Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Abweichung zur Vorlage prüfen

template_diff_check
Read-only

Vergleicht deinen finalen Brief mit der Vorlage und zeigt dir, wo du abgewichen bist. Bei einer Blockvorlage übergibst du finalBlocks statt finalContent; verglichen werden die Texte in Lesereihenfolge. Kostenlos und rein lesend. EN: Compares your final letter with the template and shows you where you deviated. For a block template pass finalBlocks instead of finalContent; the texts are compared in reading order. Free and read-only.

Input Schema

NameRequiredDescriptionDefault
reasoningNo
versionIdNoOptional: bestimmte Version, sonst die freigegebene. EN: Optional: a specific version, otherwise the released one.
templateIdYesId der Vorlage aus template_list / template_get. EN: The template ID from template_list / template_get.
finalBlocksNoDeine finalen Blöcke, wenn der Brief strukturiert ist. Verglichen werden die Texte in Lesereihenfolge. EN: Your final blocks when the letter is structured. The texts are compared in reading order.
mergeFieldsNoZuordnung der Platzhalter-Namen zu Werten, z. B. { "provider": "Telekom" }. EN: Mapping of placeholder names to values, e.g. { "provider": "Telekom" }.
finalContentNoDein finaler Brieftext. Bei einem Blockbrief stattdessen finalBlocks. EN: Your final letter text. For a block letter use finalBlocks instead.
finalSubjectYesDein finaler Betreff. EN: Your final subject line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / finalBlocks / description
      Previous value: -"Deine finalen Bloecke, wenn der Brief strukturiert ist. Verglichen werden die Texte in Lesereihenfolge. EN: Your final blocks when the letter is structured. The texts are compared in reading order."New value: +"Deine finalen Blöcke, wenn der Brief strukturiert ist. Verglichen werden die Texte in Lesereihenfolge. EN: Your final blocks when the letter is structured. The texts are compared in reading order."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this ('rein lesend' / read-only) while adding non-annotation value: the operation is free, texts are compared in reading order, and it is purely a comparison (no mutation). It stops short of noting pagination or output shape.

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?

Front-loads the core action ('Vergleicht deinen finalen Brief mit der Vorlage') and keeps each sentence purposeful within DE and EN. The bilingual duplication doubles length, but neither language version wastes words.

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?

With no output schema and a moderate 7-param tool, the description covers the essential behavior: what is compared, the block-vs-content input mode, and that it is read-only/free. Return-format detail ('shows where you deviated') is thin but sufficient for a diff tool.

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 high (86%), so the schema documents most parameters itself. The description clarifies the finalBlocks-vs-finalContent choice and the reading-order comparison semantics, but that overlap largely restates schema text, so it adds only marginal meaning. Baseline 3 is appropriate.

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 (compares) and resource (final letter vs. template) with a clear outcome (shows where you deviated). An agent can distinguish this from preview/apply siblings, though no sibling is named for contrast.

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?

Gives a conditional routing rule ('Bei einer Blockvorlage übergibst du finalBlocks statt finalContent'), which is useful for choosing between input modes. However, it offers no when-to-use vs. alternatives (e.g. template_preview, template_apply_with_merge_fields) guidance, so selection context is only implied.

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