Skip to main content
Glama

FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP

preview_datev_extf_csv_2_rows

Free 2-row taste-test preview of German DATEV Buchungsstapel EXTF v700 CSV generation (SKR03 / SKR04).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preview_datev_extf_csv_2_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
skrNoSKR03
entriesNo
bookingsNo
clientNumberNo
consultantNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does usefully disclose the hard 2-row truncation and that the call is free, which is the key behavioral trait. It omits whether output is returned inline versus written to a file, and whether any state is created server-side.

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 with no filler, and the artifact being previewed leads. The words 'free' and 'taste-test' are slightly promotional but do convey cost and sample-size information.

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

Completeness2/5

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

For a five-parameter tool with no annotations, no output schema and zero parameter documentation, the description is too thin: nothing explains the return shape, the entries-vs-bookings distinction, or the defaults for client/consultant numbers. It names the artifact but not enough to call it reliably.

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

Parameters2/5

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

Schema coverage is 0% across five parameters, and the description only touches the SKR03/SKR04 choice. The two array parameters, 'entries' and 'bookings', are left completely undifferentiated, and clientNumber/consultantNumber semantics are unexplained, so an agent cannot confidently populate 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?

States a specific action and artifact: a 2-row preview of German DATEV Buchungsstapel EXTF v700 CSV generation, with the SKR03/SKR04 variants named. That format specificity effectively separates it from the SEPA, NACHA, BAI2 and e-invoice siblings, though no sibling is named explicitly.

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?

'Free 2-row taste-test preview' implies the tool is for sampling output before a real export, but it never says when to prefer it over a full generation call, nor what to do after previewing. Usage is implied rather than stated.

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.