Skip to main content
Glama
Sign In

GUTHMANN® Berlin Real Estate

by estate.guthmann
OverviewDiscussionsAdmin

Field Metadata

field_metadata
Read-onlyIdempotent

Returns field definitions for interpreting API responses.

Use this to understand fields, units, data types, and sources.

Parameters:

  • domain (optional): specific domain for detailed field information

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

Available domains:

  • berlin: geographic reference data — Boroughs (Bezirke), Districts (Ortsteile), Neighborhoods (LOR Planungsräume)

  • immobilienmarkt.berlin.wohnungen: Berlin apartment market

  • immobilienmarkt.berlin.mehrfamilienhaeuser: Berlin apartment buildings

  • makrooekonomie.kapitalmarkt: mortgage lending rates, Bund yields

  • makrooekonomie.geldpolitik: ECB policy rates

  • makrooekonomie.arbeitsmarkt: unemployment, employment

Without a domain parameter: returns an overview of all available domains.

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

Input Schema

NameRequiredDescriptionDefault
domainNoDomain für Feld-Metadaten. Weglassen für Übersicht aller Domains.
localeNoSprache für Labels und Beschreibungen (Standard: de)de

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered; the description usefully adds what the payload contains conceptually (units, data types, sources) and how the response changes when domain is omitted. It does not describe the shape of the returned metadata records, which is the remaining gap.

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 purpose sentence, then a short usage note, then parameter and domain lists — well structured and scannable. The domain enumeration is the bulkiest section and, because it is incomplete, costs more words than it earns.

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?

With no output schema, the description carries the burden of explaining returns and does so at a conceptual level (field definitions covering units, types, sources, plus an overview mode). The partial domain list is the main incompleteness, though the schema enum backstops it.

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 both enums are already documented in the schema, so the baseline is 3. The description does add the omission behavior and locale effect, but its 'Available domains' list shows only 6 of the 21 enum values (omitting the Germany market, makrooekonomie.preise/wirtschaft, and all soziodemografie domains), which looks exhaustive and could steer an agent away from valid options.

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 ('Returns field definitions for interpreting API responses') and makes clear this is a metadata lookup rather than a data fetch, which cleanly separates it from the many data-bearing siblings such as market_berlin_apartments or macro_ecb_policy_rates.

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 a clear use case ('use this to understand fields, units, data types, and sources') and explains the two calling modes: with a domain for detail, without one for an overview of all domains. It stops short of explicitly saying to call it after/before specific sibling tools, so the routing to alternatives is implied rather than stated.

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