Skip to main content
Glama

Notarkosten berechnen

notarkosten_berechnen
Read-onlyIdempotent

Use when someone asks what a German notary charges for a will or a power of attorney: "Was kostet ein Testament beim Notar", "Notarkosten Vorsorgevollmacht", "Berliner Testament Notar Kosten", "Erbvertrag Kosten", "Vollmacht beglaubigen lassen Kosten". Computes the fee under the German court and notary fees act (GNotKG, Tabelle B, as amended 2025) from the document type and the assets in euros: business value (Geschäftswert), fee rate, minimum fees, postage flat rate (Nr. 32005 KV), 19 % VAT and the total. For wills it also compares notary, lawyer and handwritten will with court custody and register fees. Only the document type and an amount are needed; never ask for a name or other personal details.

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": {
      "dokument": "<dokument>",
      "vermoegen": "<vermoegen>"
    },
    "name": "notarkosten_berechnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
dokumentYestestament = Einzeltestament; gemeinschaftliches_testament = Berliner Testament oder Erbvertrag (2,0-Gebühr); vorsorgevollmacht_beurkundet = notarielle Beurkundung; vorsorgevollmacht_beglaubigt = nur Unterschriftsbeglaubigung unter einem fertigen Text.
schuldenNoSchulden in Euro, optional. Zählen nur beim Testament, höchstens bis zur Hälfte des Vermögens (§ 102 GNotKG).
vermoegenYesVermögen in Euro (Aktivvermögen, bei Ehepaaren gemeinsam). Eine Schätzung genügt.

Output Schema

NameRequiredDescriptionDefault
nettoYes
bruttoYes
gebuehrYes
quellenYes
dokumentYes
hinweiseYes
schuldenNo
vergleichNo
vermoegenNo
disclaimerYes
rechner_urlYes
umsatzsteuerYes
dokument_textNo
gebuehrensatzNo
hoechstbetragYes
geschaeftswertYes
auslagenpauschaleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context: the legal basis and 2025 amendment, that VAT is 19% and postage is Nr. 32005 KV, and that wills additionally include a cost comparison — none of which is derivable from the annotations.

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 the use case and followed by scope and the data-minimization rule. The list of example queries is long but directly supports trigger matching; the enumeration of fee components partly duplicates what the output schema would reveal, which is the only waste.

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?

An output schema exists, so return values need not be explained, yet the description still names the computed components for predictability. Legal basis, input minimality, and the extra will-comparison behavior are all covered — nothing an agent needs to invoke this correctly is missing.

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?

With schema coverage at 100% and the enum fully documented inline, the schema already carries the semantic load, so baseline 3 applies. The description only restates that document type and an amount suffice and hints at the business value concept; it adds little beyond the existing parameter descriptions.

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: computes German notary fees under GNotKG Tabelle B from document type and asset value. Lists exactly which outputs are produced (fee rate, minimum fees, postage flat rate, VAT, total) and adds a comparison feature for wills, so an agent can tell it apart from erbquoten_berechnen or vorsorge_fakten without opening any schema.

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?

Opens with an explicit trigger condition ('Use when someone asks what a German notary charges for a will or a power of attorney') backed by five realistic phrasings. Also gives a negative constraint — never ask for a name or personal details — and states the minimal input needed, which removes the main failure mode for this tool.

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