Skip to main content
Glama

Gebührenkatalog nachschlagen

rvg_fee_catalog
Read-onlyIdempotent

Liefert Gebührentatbestände mit Katalog-Schlüssel, Sätzen und Tabellen zum Stichtag. Rufe es, bevor du eine VV-Nummer, einen Satz oder eine Bezeichnung nennst. Beträge nur über rvg_calculate. Erfinde keine Nummer und keinen Satz. Schlag mit keys nur die Nummern nach, die du brauchst; ohne keys kommt der ganze Katalog (rund 45 KB). Unter positionTypes stehen die Auslagen (Nr. 7000 ff.), die Erhöhung Nr. 1008 und die Positionstypen ohne VV-Nummer, je mit Pflichtfeldern und Satz bzw. Deckel zum Stichtag; unter roleFees die Gebühren nach Teil 4 und 5 VV (Straf- und Bußgeldrecht) mit Rahmen, Festbetrag und Pflichtfeldern. Der Katalog-SCHLÜSSEL (nicht das Feld vvNummer) ist das, was rvg_calculate erwartet: Nr. 1000 gibt es zweimal, als '1000' und '1000-2'. Unter creditingSources stehen die Anrechnungsquellen; ihre id gehört in quelleKatalogId einer Anrechnung. Die Tabellenwerte sind zum Nachschlagen da, nicht zum Selberrechnen. Die GKG-Tabelle ist kein Gerichtskostenrechner: Gerichtskosten beziffert ONYST nicht, nenne sie nicht als Betrag.

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

Input Schema

NameRequiredDescriptionDefault
keysNoNur diese Katalog-Schlüssel, z. B. ["2100", "3200", "7002"]; "1000" bringt "1000-2" mit. Dazu kommen ihre Anrechnungsquellen und die Tabellen. Ohne Angabe: der ganze Katalog.
effectiveDateNoStichtag im Format JJJJ-MM-TT (§ 60 RVG: der Auftragstag, nicht der heutige). Ohne Angabe: heute.

Output Schema

NameRequiredDescriptionDefault
feesYes
feeTableYes
roleFeesYes
effectiveDateYes
positionTypesYes
courtCostTableYes
creditingSourcesYes
assignedCounselFeeTableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, and the description adds substantive behavior the annotations cannot: the ~45 KB payload size when keys are omitted, the internal section layout (positionTypes, roleFees, creditingSources), the key-vs-vvNummer trap, and the explicit negative scope that GKG values are lookup-only and not a court-fee calculator.

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-loaded with purpose, then guardrails, then a structural map of the response — a sensible order for an agent. It is dense rather than padded, though the anti-fabrication theme recurs across three sentences ('Erfinde keine Nummer', 'nicht zum Selberrechnen', 'nenne sie nicht als Betrag'), which costs a little tightness.

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?

For a two-parameter lookup with an output schema and full annotation coverage, nothing an agent needs is missing: it knows when to call, how to scope the payload, which key format to use, and what not to do with the returned tables.

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 already 100%, so the schema documents both fields; the description nonetheless adds critical meaning the schema lacks — that the catalog key (not the vvNummer field) is what rvg_calculate consumes, and that '1000' exists twice as '1000' and '1000-2'. It does not restate the maxItems limit or the date format, which the schema handles.

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 and resource ('Liefert Gebührentatbestände mit Katalog-Schlüssel, Sätzen und Tabellen zum Stichtag') and immediately partitions the domain against the sibling by declaring 'Beträge nur über rvg_calculate'. An agent knows exactly what comes back and what does not.

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?

Explicit when-to-use ('Rufe es, bevor du eine VV-Nummer, einen Satz oder eine Bezeichnung nennst'), an explicit alternative for the calculation path (rvg_calculate), and a concrete decision rule for the key parameter including the cost of omitting it ('ohne keys kommt der ganze Katalog (rund 45 KB)'). Nothing is left to inference.

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