Skip to main content
Glama
Sign In
csv2zugferd

csv2zugferd

by rillsoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get configuration reference

csv2zugferd_config_schema_get
Read-onlyIdempotent

Returns the CSV-to-ZUGFeRD YAML configuration schema, including every key's type, default, allowed values and resolution semantics. Request a section subtree before drafting or validating a mapping.

Instructions

Returns the reference of the csv2zugferd YAML configuration: a JSON Schema of every key with description, type, default and allowed values, plus semantics per key (effect, mode dependency, resolution order value > column > rules > default, fallback for unknown values). Use it before drafting a configuration; no README is needed. The complete reference is about 100 KB; pass section (for example mapping.lineItems) to get one subtree with its definitions. Does not check a concrete configuration (use csv2zugferd_config_get). Read-only.

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": "csv2zugferd_config_schema_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoOptional configuration path to return only that subtree with the definitions it uses, for example zugferd, mapping.lineItems or mapping.paymentMeans. Semantics are filtered to the same subtree.

Output Schema

NameRequiredDescriptionDefault
schemaYesJSON Schema (Draft 2020-12) of the whole YAML configuration (or of the section) with descriptions, defaults and value sets; $defs holds the shared definitions used.
sectionYesThe section argument as given, or null for the complete reference.
semanticsYesEffect, modes, resolution sources and value sets per configuration path (filtered to the section when given).
schemaVersionYescsv2zugferd version the schema was generated from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover read-only/idempotent/non-destructive, but the description adds genuinely new behavior: the full response is roughly 100 KB, section filters both schema and semantics to a subtree, semantics disclose resolution order (value > column > rules > default) and fallback behavior for unknown values. The payload-size warning is materially useful for an agent managing context.

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 what is returned, then usage, then filtering, then the exclusion — a sensible order with dense sentences. Minor waste in the closing 'Read-only.' which only restates the annotations, and 'no README is needed' is padding, but overall it is tight for the amount of behavior conveyed.

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

Completeness5/5

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

Output schema exists, so return values need no prose explanation, and the description still supplies the practical facts an agent needs: total payload size, how to narrow it, what the semantics fields mean, and which sibling performs validation. Nothing required to invoke it correctly is missing.

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?

Schema coverage is 100% and the enum already documents every valid path, so the structured data does most of the work. The description still adds value by giving a concrete example ('mapping.lineItems') and clarifying that semantics are filtered to the same subtree, which the schema description states but the tool description reinforces with the size trade-off.

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?

Names a specific verb and resource ('Returns the reference of the csv2zugferd YAML configuration') and enumerates the returned content (JSON Schema of every key with description, type, default, allowed values, plus per-key semantics). It also explicitly distinguishes itself from the sibling by stating it does not check a concrete configuration and naming csv2zugferd_config_get as the tool that does.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it before drafting a configuration'), an explicit anti-trigger ('Does not check a concrete configuration (use csv2zugferd_config_get)'), and a strategy for large payloads (pass section). The agent knows when to call this, when to call the sibling, and how to scope the call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools