Skip to main content
Glama

getecoback-climate-weather

stromjournal_mehrfachzahlung_kandidat

Read-only

Zwei gleich hohe Zahlungszeilen im privaten Haushaltsbuch nach Belegbezug und Datumsabstand einordnen — Flag a possible duplicate payment without deleting entries.

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": {
      "a_cent": "<a_cent>",
      "b_cent": "<b_cent>",
      "abstand_tage": "<abstand_tage>",
      "suchradius_tage": "<suchradius_tage>",
      "belegbezug": "<belegbezug>"
    },
    "name": "stromjournal_mehrfachzahlung_kandidat"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_centYesErste gespeicherte Abbuchung in Cent.
b_centYesZweite gespeicherte Abbuchung in Cent.
belegbezugYesLaut vorliegenden Unterlagen betreffen die Zeilen denselben Beleg?
abstand_tageYesAbsoluter Abstand der Buchungsdaten in Tagen.
suchradius_tageYesSelbst gewählte maximale Zahl an Tagen für den Suchhinweis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the 'without deleting entries' phrasing mainly reinforces structure rather than adding new safety information. What the description does add is that the output is a heuristic 'flag' rather than a confirmed verdict, which matters. It still does not say what the flag contains (e.g., suspicion levels or a recommendation) even though no output schema exists to cover that.

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?

A single front-loaded sentence that names the object, the criteria, and the safety constraint in that order, with no filler. The German-then-English construction is slightly redundant but adds a useful one-line restatement rather than padding.

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?

All five parameters are required and there is no output schema, so the description bears more weight than it delivers: it never states what the agent receives back from a duplicate check. For a read-only computation tool that is the main remaining gap; the purpose and criteria side is adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3, and the description earns a step up by clarifying that a_cent and b_cent must be of equal amount and that belegbezug plus abstand_tage are the two assessment criteria. It does not explain how suchradius_tage changes the outcome, but most parameter meaning is already carried by the schema.

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?

The description states a concrete verb and resource: two equal-amount payment lines in a private household ledger are to be classified ('einordnen') by receipt reference and date gap, resulting in a duplicate-payment flag. That is specific enough to distinguish it from a plain ledger-state tool like stromjournal_zahlungszustaende, though the sibling is never named.

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 intended situation is implied — comparing two same-amount postings for a duplicate — and 'without deleting entries' hints this is the safe, non-destructive check. But there is no explicit when-to-use versus when-not guidance, no mention of preconditions, and no routing to alternatives for the case where the amounts differ or the receipt reference is unclear.

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.

Resources