Skip to main content
Glama
telota

bbaw-dse-mcp

by telota

mop_search_residential_topography

Find historical persons and institutions in residential address data using filters for name, location, profession, or category.

Instructions

Search residential topography data with multiple filters.

PURPOSE: Find persons/institutions by various criteria in historical address data.

WHEN TO USE:

  • User searches for specific person by name

  • User wants to know who lived at a specific address

  • User wants to filter by profession, category, or location

  • User needs to find all court members in a certain category

WHEN NOT TO USE:

  • For biographical details → use get_register_entry()

  • For full dataset overview → use get_residential_topography()

Args: year: Year for data (1800, 1845, 1872, 1891, or 1914) name: Last name (partial match, case-insensitive) vorname: First name (partial match, case-insensitive) kategorie: Category filter (e.g., "Königliche Familie", "Diplomatie") taetigkeit: Occupation/activity filter stadt: City filter (partial match) strasse: Street name filter (partial match) ediarum_id: Exact Ediarum-ID match only_with_coordinates: Return only entries with valid geographic coordinates max_results: Maximum number of results to return ctx: FastMCP Context

Returns: Dict with: - year: The queried year - filters_applied: List of active filters - total_matches: Number of matching entries - returned_results: Number of results in response (limited by max_results) - results: List of matching features

Raises: ToolError: If year is not available or no filters provided

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
yearYes
stadtNo
strasseNo
vornameNo
kategorieNo
ediarum_idNo
taetigkeitNo
max_resultsYes
only_with_coordinatesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are present, so the description carries the full burden. It discloses critical behavioral traits: filtering semantics (partial match, case-insensitive), valid year values, raising ToolError for unavailable years or missing filters, and returning a structured dict with counts and results. This goes beyond a basic search tool description.

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?

The description is well-structured with clear sections (PURPOSE, WHEN TO USE, WHEN NOT TO USE, Args, Returns, Raises). While it is somewhat long, the length is justified by the 10 parameters and the need to compensate for unschema-documented properties. It could be slightly trimmed, but no content is wasted.

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?

Given 10 parameters, no annotations, and no schema descriptions, this description is remarkably complete. It covers purpose, usage contexts, parameter semantics, return structure, and error conditions. The output schema exists, but the description adds necessary filter behavior and validation details, making it self-sufficient for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description documents every parameter with meaningful detail: year lists valid values, name/vorname specify partial match and case-insensitivity, only_with_coordinates explains its filtering effect, and max_results is described in the return section. This fully compensates for the schema's lack of descriptions.

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?

The description clearly states 'Search residential topography data with multiple filters' and further defines the purpose as 'Find persons/institutions by various criteria in historical address data.' It also distinguishes itself from siblings by explicitly naming get_register_entry and get_residential_topography as alternatives in the WHEN NOT TO USE section.

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

Usage Guidelines5/5

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

The description provides dedicated WHEN TO USE and WHEN NOT TO USE sections, listing concrete scenarios (e.g., searching by person, address, profession) and explicitly naming alternative tools for other needs. This is exemplary usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/telota/bbaw-dse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server