Skip to main content
Glama

Gutachten AfA – Restnutzungsdauer & Kaufpreisaufteilung

Restnutzungsdauer & AfA-Satz schätzen

restnutzungsdauer_vorschau
Read-onlyIdempotent

Unverbindliche Vorschau der Restnutzungsdauer und des möglichen AfA-Satzes nach dem Modernisierungspunkte-Modell (Anlage 2 ImmoWertV) – identisch mit der Sofortberechnung im Auftragsformular. Ersetzt kein Gutachten.

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": {
      "baujahr": "<baujahr>"
    },
    "name": "restnutzungsdauer_vorschau"
  }
}

Input Schema

NameRequiredDescriptionDefault
baujahrYes
stichtagNoYYYY-MM-DD, z. B. Übergang von Nutzen und Lasten. Standard: heute.
immobilienartNoBestimmt die Gesamtnutzungsdauer. Standard: Eigentumswohnung (80 Jahre).
modernisierungNoModernisierungen bis zum Stichtag. Nicht modernisiert = prozent 0. Nur echte Verbesserungen, keine Instandhaltung. Mehrere Teilmaßnahmen pro rata zu einem fiktiven Jahr zusammenfassen und dann prozent 100 angeben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds value beyond them by qualifying the result as non-binding, naming the legal basis of the calculation, and stating it is identical to the instant calculation in the order form. Pagination/return format is not covered, but for a pure local estimate that matters little.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the tool's output and method, followed by the parity note and the disclaimer. Every clause carries information and nothing is repeated from the schema.

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

Completeness4/5

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

For a tool with a deep nested schema and no output schema, the description still names both outputs (Restnutzungsdauer, AfA-Satz) and frames the result as an estimate. What is missing is minor: no indication of units or that the AfA rate is a percentage derived from the remaining life.

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?

Schema coverage is 75% and the nested modernisierung object already carries per-field descriptions, including the non-trivial aggregation rule (pro rata zu einem fiktiven Jahr zusammenfassen, dann prozent 100). The description itself adds no parameter meaning, so the baseline 3 is appropriate for high-coverage 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 verb+resource pair: an unverbindliche Vorschau of Restnutzungsdauer and möglicher AfA-Satz, with the calculation method named (Modernisierungspunkte-Modell, Anlage 2 ImmoWertV). An agent immediately knows what it computes, though no sibling (e.g. gutachten_afa_info, gutachten_afa_preise) is named to sharpen the boundary.

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?

"Unverbindliche Vorschau" and "Ersetzt kein Gutachten" set a clear boundary on when the result is appropriate, and the note that it matches the Sofortberechnung im Auftragsformular signals its place in the workflow. However, no alternative tool is named for the case where a binding valuation or AfA price info is actually needed, so routing 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