Skip to main content
Glama
Sign In

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Standardvorlagen übernehmen

template_clone_from_library
Destructive

template_clone_from_library kopiert ein bis fünf FrankKi-Standardvorlagen in einem Aufruf in die eigenen Vorlagen des Kontos, etwa Rechnung, Mahnung, Angebot, Kündigung oder Behördenpost, und zeigt die erste als Bild. Mit release true gibt es sie frei, wenn das Konto genau einen aktiven Nutzer hat. Danach sendet order_send mit templateId und templateVersionId. EN: template_clone_from_library copies one to five FrankKi standard templates into the account's own templates in one call, such as invoice, dunning letter, quote, cancellation or letters to authorities, and shows the first as an image. With release true it releases them on a single-user account. Then order_send sends with templateId and templateVersionId.

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": {
      "items": "<items>"
    },
    "name": "template_clone_from_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesIds aus mcp_health oder template_list (curated). EN: Ids from mcp_health or template_list (curated).
releaseNoGibt frei, wenn das Konto genau einen aktiven Nutzer hat. EN: Releases on a single-user account.
reasoningNo
previewFirstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / maxItems
      Previous value: -3New value: +5
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds genuinely useful context (shows the first template as an image, release only works on a single-user account, the follow-up send flow). However, for a tool flagged destructive it never says what could be lost — e.g. whether an existing template with the same name is overwritten — which is the most important behavioral fact here.

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 action and its constraints are front-loaded, which is good, but the entire text is repeated verbatim in German and English, roughly doubling length without adding information. Useful content is present but half the tokens are redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does explain the visible result (first template rendered as an image) and the next workflow step, which is solid. Still missing for a destructive, account-mutating tool: failure modes, name-collision behavior, and what happens to the remaining templates when previewFirst is used.

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%. The description covers items (one to five templates) and release (single-user account prerequisite), and 'shows the first as image' implicitly explains previewFirst's default. reasoning and the name field are left entirely to the schema, so the description neither compensates for the coverage gap nor contradicts it.

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: copies one to five FrankKi standard templates into the account's own templates in a single call, with concrete examples (invoice, dunning letter, quote). An agent can distinguish this from template_save (authoring) and template_list (source of IDs) without opening the schema, though the differentiation is implicit rather than stated.

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

Usage Guidelines4/5

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

Gives concrete routing: IDs come from mcp_health or template_list (curated), and the downstream step is order_send with templateId and templateVersionId. The release prerequisite (exactly one active user) is also stated. It lacks an explicit 'do not use this when…' exclusion, so it stops short of a 5.

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