Skip to main content
Glama

search_german_zvg_foreclosures

Search German real estate foreclosure auctions on zvg-portal.de and filter results by city, state, postal code, property type, market value, and auction status.

Instructions

Search German real estate foreclosure auctions (Zwangsversteigerungen) on zvg-portal.de.

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

Input Schema

NameRequiredDescriptionDefault
cityNoFilter auctions by city name, e.g. 'Leipzig' or 'Berlin'.
statesNoFederal state codes or names, e.g. ['by', 'be', 'sn'] or ['ALL'].
max_itemsNoMaximum number of foreclosure properties to return (1-5000).
postal_codeNoFilter by 5-digit German postal code, e.g. '04109'.
property_typeNoProperty category filter.ALL
exclude_expiredNoExclude auctions whose scheduled date/time has already passed.
include_detailsNoFetch full descriptions, auction location, land register, and appraisal PDF URLs.
max_market_valueNoMaximum judicial market valuation (Verkehrswert) in EUR.
min_market_valueNoMinimum judicial market valuation (Verkehrswert) in EUR.
include_cancelledNoInclude cancelled foreclosure auctions.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about how the tool behaves: that it scrapes an external portal, expected latency, pagination or result ordering, or that include_details triggers additional per-listing fetches. Naming the source domain is the only behavioral hint, and it is thin for a 10-parameter scraping tool.

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?

A single front-loaded sentence with no filler, and the key identifiers (German, foreclosure auctions, source portal) come first. It is efficient but arguably undersized for a tool of this complexity, which is penalized under completeness rather than here.

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

Completeness2/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-value explanation is not required, and the parameters are fully self-documented. However, for a 10-parameter, unannotated scraping tool with filters for expired/cancelled auctions and valuation ranges, the description omits any behavioral or selection context an agent would need to call it confidently.

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 description coverage is 100% and all ten parameters are documented in the schema with examples (city names, state codes, postal codes, EUR valuation bounds). The description adds no meaning beyond that, so the baseline 3 applies.

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 gives a specific verb+resource (search foreclosure auctions), names the German term Zwangsversteigerungen, and identifies the source site zvg-portal.de, which is enough to distinguish it from all listed siblings (tenders, KYB, impressum, B2B leads, einvoice). It stops short of explicit sibling differentiation, which the siblings' distinct domains make largely unnecessary.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives for adjacent needs (e.g. public tenders vs. foreclosure auctions). Usage is only implied by the resource name.

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