Skip to main content
Glama
Sign In

GUTHMANN® Berlin Real Estate

by estate.guthmann
OverviewDiscussionsAdmin

Listing Details

listing_details
Read-onlyIdempotent

One GUTHMANN listing in detail: prices and running costs, areas, amenities, energy certificate, exposé texts, images, contact and the exposé URL on guthmann.estate. When the address is not released, street/house number are null and the coordinate is deterministically offset by 150-300 m (koordinaten_versetzt = true).

Parameters:

  • public_id: public listing id (hex, from listings or the exposé URL)

  • locale: "de" | "en" (default: en)

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": {
      "public_id": "<public_id>"
    },
    "name": "listing_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoSprache für Titel, Texte und Exposé-URLen
public_idYesÖffentliche Objekt-ID (Hex, aus der Exposé-URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / locale / description
      Added value: +"Sprache für Titel, Texte und Exposé-URL"
    • addedInput schema / properties / public_id / description
      Added value: +"Öffentliche Objekt-ID (Hex, aus der Exposé-URL)"
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses a non-obvious data behavior: when the address is withheld, street/house number are null and coordinates are deterministically shifted 150–300 m with koordinaten_versetzt = true. That caveat materially affects how an agent interprets geodata and is not derivable from the schema.

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?

Front-loaded with the resource and its content, followed by the anonymization caveat and a short parameter block. The explicit 'Parameters:' list partially duplicates the schema's enum/default text, a small amount of redundancy but the ordering and wording stay tight.

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 two-parameter read-only detail tool with no output schema, the description covers returned fields and the main data caveat adequately. It does not mention error behavior for an invalid or unknown public_id, which is the remaining minor gap.

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%, so the schema already documents both parameters. The description mostly restates them (hex id, locale enum and default), adding only the provenance hint that the id also comes from the listings tool; this is marginal value 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 and resource ('One GUTHMANN listing in detail') and enumerates the returned content (prices, areas, amenities, energy certificate, exposé texts, images, contact, URL), which clearly separates it from the plural sibling 'listings'. An agent can identify this as the single-record fetch without opening the schema.

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?

The public_id parameter note ('from listings or the exposé URL') implicitly routes the agent to the listing list tool first when an id is unknown, and the 'One ... listing' framing signals the single-record use case. No explicit when-not-to-use or exclusion statement is given, keeping it below a 5.

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

All GUTHMANN® Berlin Real Estate 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