Skip to main content
Glama

Gutachten AfA – Restnutzungsdauer & Kaufpreisaufteilung

Gutachten AfA: Preise

gutachten_afa_preise
Read-onlyIdempotent

Aktuelle Preise (inkl. USt.) für Restnutzungsdauergutachten, Vor-Ort-Besichtigung, Express und Kaufpreisaufteilung; berechnet optional den Gesamtpreis für eine Leistungskombination. Die Kosten sind als Werbungskosten absetzbar.

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

Input Schema

NameRequiredDescriptionDefault
expressNo
kaufpreisaufteilungNo
vor_ort_besichtigungNo
anzahl_besichtigungenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the bar is lower. The description does add real context: prices include VAT, a combination total is computed on request, and costs are tax-deductible – none of which is in the annotations. It does not say whether prices are per-unit or flat, nor how multiple selected services are summed.

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?

Two compact sentences, front-loaded with the priced services before the optional aggregation. No filler, though the closing tax-deductibility remark is informative rather than operational and adds little for tool selection.

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

Completeness3/5

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

For a read-only pricing tool with four parameters, no output schema and 0% schema coverage, the description should explain the shape of the returned pricing data and what anzahl_besichtigungen does. It covers the service catalog and the combination logic but leaves the counting parameter and the return structure opaque.

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 0%, so the description carries the burden; it names three of the four parameters in prose and explains that the booleans act as selectors whose combination yields a total, which is genuine meaning beyond the schema. However, anzahl_besichtigungen is never mentioned, and the remaining parameters get no semantics beyond their German labels – e.g. no unit price, no cap behavior.

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 concrete resource (current prices incl. VAT) and enumerates the priced services – Restnutzungsdauergutachten, Vor-Ort-Besichtigung, Express, Kaufpreisaufteilung – plus the optional combination total. An agent can tell this is a price lookup, not an ordering tool. It does not explicitly distinguish itself from gutachten_afa_info, so it stops short of a 5.

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?

Implies usage (fetch prices before quoting/ordering, optionally compute a bundle total) but never states when to pick this over gutachten_afa_info or restnutzungsdauer_vorschau. No prerequisites, no exclusions, no follow-up routing – the agent must infer the workflow.

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