Skip to main content
Glama

immobilien

fetch_property

Liefert die vollständigen Details zu einer Immobilienanzeige anhand ihrer id (aus search_properties): Beschreibung, Anbieter (seller), Ausstattung (features: terrasse, parkplatz, aufzug, keller) und listing_url. listing_url ist der Link zum Exposé auf dem Original-Portal. WICHTIG: listing_url NICHT selbst aufrufen oder abrufen — gib den Link dem Nutzer als anklickbaren Link aus, damit er das Exposé bei Interesse selbst öffnet.

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": {
      "id": "<id>"
    },
    "name": "fetch_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDie id eines Treffers aus search_properties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does meaningful work: it lists the returned data shape and adds a non-obvious operational constraint — never dereference listing_url, hand it to the user as a clickable link instead. What it omits is authentication requirements, rate limits, and failure behavior for an unknown id.

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 core purpose, then the return fields, then the important listing_url warning in caps so it is not skimmed past. It is three sentences and largely earns its length, though the field enumeration and the earlier parenthetical overlap slightly.

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 single-parameter read tool with no output schema, the description is nearly self-sufficient: it names the returned fields, the id's provenance, and the key interaction constraint. Only edge cases like invalid or expired ids are left unaddressed, which is a minor gap at this complexity.

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% and the single id parameter is already documented in the schema as coming from search_properties, so the description's '(aus search_properties)' largely repeats structured data. It adds no format, length, or example detail beyond that, so baseline 3 applies.

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 ('Liefert die vollständigen Details zu einer Immobilienanzeige anhand ihrer id') and enumerates exactly what comes back (Beschreibung, seller, features, listing_url). It also anchors itself against the sibling by naming search_properties as the source of the id, so the agent can tell fetch from search without opening a 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 usage path is clear: take the id from search_properties and call this to get full details, which implicitly makes this the second step after searching. It also gives an explicit do-not rule for listing_url. It does not spell out a when-not-to-use case (e.g. calling this without first searching), so it falls just short of the top band.

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