Skip to main content
Glama
Sign In

Austria Property

by io.github.mastalier1997
OverviewDiscussionsAdmin

Statutory rules and assumptions

get_rules
Read-onlyIdempotent

List the statutory values the engine uses on a date (tax and fee rates, broker caps, minimum repair reserve, MRG cut-off dates, Richtwerte per state, AfA rates, land shares, income tax brackets), each with legal basis, source URL and the date it was last verified, plus the default assumptions and risk thresholds. Use to cite sources or to explain how a number was calculated.

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

Input Schema

NameRequiredDescriptionDefault
dateNoReturn the rules valid on this date, YYYY-MM-DD. Defaults to today (Vienna time).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, closed world), but the description adds substantive detail beyond them: each value ships with legal basis, source URL and last-verified date, plus default assumptions and risk thresholds, and results are scoped to a validity date. With no output schema, this return-shape disclosure is genuinely useful, though pagination/volume is unaddressed.

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 sentences, front-loaded with the core action and then the use case. The long parenthetical enumeration of rule categories is dense but every item earns its place by telling the agent what data is available.

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 single-parameter lookup with no output schema, the description fully characterizes the response: values plus legal basis, source URL, verification date, and the accompanying assumptions and risk thresholds. An agent has everything needed to call it and to interpret the result.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents the YYYY-MM-DD format and the 'defaults to today (Vienna time)' behavior. The description only implies date-scoped validity ('the engine uses on a date'), which the schema states anyway, so it adds no meaning beyond structured data.

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 ('List the statutory values the engine uses') and enumerates the concrete domain content: tax and fee rates, broker caps, repair reserve, MRG cut-offs, Richtwerte, AfA rates, land shares, income tax brackets. This makes it unmistakably a reference/lookup tool, cleanly separable from the calculating siblings estimate_acquisition_costs and underwrite_property.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit positive triggers: 'Use to cite sources or to explain how a number was calculated.' This tells the agent when to reach for it (auditing/explaining results from the sibling calculators) but never states when not to use it or names the siblings it complements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Austria Property toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources