Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Auswertungen abrufen

analytics_summary
Read-only

Liefert die aggregierten Kennzahlen des Partnerkontos: Briefe pro Monat, Kosten pro Mandant zur Weiterberechnung, Laufzeiten bis zur Zustellung, Fehlerquoten und Ausgaben gegen die gesetzten Limits. Beträge sind Netto-Kosten in Cent. EN: Returns the partner account's aggregated metrics: letters per month, cost per mandant for rebilling, transit times to delivery, failure rates, and spend against configured limits. Amounts are net cost in cents.

Input Schema

NameRequiredDescriptionDefault
topNNoAnzahl Mandanten in cost_per_mandant, 1 bis 50, Standard 10. EN: Number of mandants in cost_per_mandant, 1 to 50, default 10.
sinceNoZeitraumbeginn für cost_per_mandant und delivery_times, zum Beispiel 2026-01-01. Standard: letzte 90 Tage. EN: Range start, for example 2026-01-01. Default: last 90 days.
untilNoZeitraumende, Standard jetzt. EN: Range end, default now.
metricNoWelche Auswertung. overview (Standard) fasst die letzten drei Monate zusammen. EN: Which report. overview (default) summarises the last three months.
monthsNoTrendlänge für letters_per_month und failure_rates, 1 bis 24, Standard 12. EN: Trend length for letters_per_month and failure_rates, 1 to 24, default 12.
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / months / description
      Previous value: -"Trendlaenge fuer letters_per_month und failure_rates, 1 bis 24, Standard 12. EN: Trend length for letters_per_month and failure_rates, 1 to 24, default 12."New value: +"Trendlänge für letters_per_month und failure_rates, 1 bis 24, Standard 12. EN: Trend length for letters_per_month and failure_rates, 1 to 24, default 12."
    • changedInput schema / properties / since / description
      Previous value: -"Zeitraumbeginn fuer cost_per_mandant und delivery_times, zum Beispiel 2026-01-01. Standard: letzte 90 Tage. EN: Range start, for example 2026-01-01. Default: last 90 days."New value: +"Zeitraumbeginn für cost_per_mandant und delivery_times, zum Beispiel 2026-01-01. Standard: letzte 90 Tage. EN: Range start, for example 2026-01-01. Default: last 90 days."
  2. First observed

TDQS

A3.7/5.0
Behavior3/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 the semantic unit ('Beträge sind Netto-Kosten in Cent'), which prevents misreading the numbers, but says nothing about caching, freshness, or result size for a metrics endpoint.

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?

The bilingual DE/EN pairing is duplicated but that is inherent to the tool's convention, and each sentence front-loads the metric list followed by the unit caveat. No filler beyond the required translation.

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, the description carries the burden of describing return content, and it does so by naming every metric family plus the amount unit. It is nearly complete for a read-only reporting tool, missing only result shape/detail per metric.

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 description coverage is high (83%), so the schema already documents topN, since, until, metric and months bounds and defaults. The description only mentions that cost_per_mandant and delivery_times are time-scoped, which the schema also states, so it adds little beyond the baseline.

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+resource ('Liefert die aggregierten Kennzahlen des Partnerkontos') and enumerates the exact metric families returned. This clearly separates it from siblings like wallet_balance or pricing_tiers, which report different data.

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 enumeration of metrics implies when the tool is relevant (reporting/rebilling overview), but it never states when to prefer it over alternatives or what prerequisite state is needed. Usage is inferred rather than directed.

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