CityDPC-MCP

Overview Schema Source Related Servers Discussions Admin

get_building_by_id

Retrieve all attributes for a specific CityGML building by its gml:id to inspect and analyze individual records in CityJSON and CityGML datasets.

Instructions

Gibt alle Informationen zu einem spezifischen Gebäude zurück.

Args: building_id: Die gml:id des Gebäudes

Returns: dict: Dictionary mit allen Gebäude-Attributen

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": {
      "building_id": "<building_id>"
    },
    "name": "get_building_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`building_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It mentions that all building attributes are returned, but says nothing about behavior when the id does not exist, permissions, or failure modes.

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?

Short and front-loaded, with the purpose in the first sentence. The Args/Returns blocks are standard docstring boilerplate, and the Returns block is largely redundant with the existing output schema.

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 lookup with an output schema, the essential facts (what it returns, what the id is) are covered. The main omission is not-found/error behavior, which matters little for this simple read.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it specifies that building_id is the gml:id of the building, information the schema (plain string) does not convey.

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?

States a specific verb and resource: returns all information for a specific building. The word 'spezifischen' implicitly distinguishes it from the list-style siblings (get_all_buildings, get_buiding_Id_list), though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the lookup-by-id tool, but the description never states when to prefer it over get_all_buildings or get_buiding_Id_list, nor any prerequisites.

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