Skip to main content
Glama

Gutachten AfA – Restnutzungsdauer & Kaufpreisaufteilung

Gutachten AfA: Leistungen & Ablauf

gutachten_afa_info
Read-onlyIdempotent

Informationen zu Gutachten AfA: Restnutzungsdauergutachten zur Verkürzung der AfA (§ 7 Abs. 4 Satz 2 EStG), Kaufpreisaufteilung, Vor-Ort-Besichtigung, Ablauf, benötigte Unterlagen, Anerkennung beim Finanzamt, Kontakt sowie Wortlaut der Erklärungen bei Auftragserteilung.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
themaNoStandard: ueberblick

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this is a knowledge/information resource rather than a live transaction, which is useful. It does not disclose the return format, whether content is static, or any limits, so it remains a moderate contribution.

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?

The definition is a single front-loaded sentence with no filler, and the key scope is stated first. The comma-separated topic list is dense and slightly hard to scan, which keeps it from a 5, but it is appropriately sized for a simple info tool.

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 low-complexity, read-only information tool with one optional enum parameter, full schema coverage and strong annotations, the description covers the essential scope. The main missing element is any statement about how the information is returned, but the overall definition is sufficient for correct selection and invocation.

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 100%, so the single 'thema' enum and its default are already fully documented. The description expands the topical meaning behind the enum values (e.g., leistungen, ablauf, unterlagen, finanzamt, kontakt, auftrag) and thus adds some contextual meaning. It does not map each enum value to its exact content, so baseline 3 is appropriate.

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?

The description opens with a clear verb-plus-resource ('Informationen zu Gutachten AfA') and enumerates the specific subject matter: Restnutzungsdauergutachten under § 7 Abs. 4 Satz 2 EStG, Kaufpreisaufteilung, Vor-Ort-Besichtigung, Ablauf, Unterlagen, Finanzamt-Anerkennung and Kontakt. This makes the tool's informational scope unmistakable. It does not explicitly differentiate itself from siblings such as preise or ersteinschaetzung, 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?

By listing the covered topics, the description implies the agent should call it when a user asks about any of those subjects. However, it gives no explicit when-to-use or when-not-to-use guidance and never names an alternative tool or routing condition. Usage is therefore inferable but not directed.

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