Skip to main content
Glama

Get building register entry by EGID

get_building
Read-only

Retrieve the official GWR/RegBL record for a Swiss building by federal EGID to inspect status, category, construction year, floors, dwellings, area, and heating data.

Instructions

Official GWR/RegBL record for a building identified by its federal EGID: status, category, construction year, floors, dwelling count, area, heating info. Get the EGID from reverse_geocode.

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": {
      "egid": "<egid>"
    },
    "name": "get_building"
  }
}

Input Schema

NameRequiredDescriptionDefault
egidYesFederal building ID (EGID), e.g. from reverse_geocode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that the source is an official federal register (authoritative, not derived) and lists what the record contains, which is real behavioral context; it stops short of describing pagination, error behavior, or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence identifying the resource and what it returns, plus one short acquisition hint. No filler or redundant restatement of the title.

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?

There is no output schema, and the field enumeration (status, category, construction year, floors, dwellings, area, heating) compensates well for that. Minor gaps remain around error handling for unknown EGIDs and the exact record format, but the tool is simple enough that nothing essential is missing.

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 egid parameter is fully documented with pattern and an example source, so the description adds little beyond restating that the EGID identifies the building. Baseline 3 is appropriate when the schema does the heavy lifting.

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 retrieval verb and resource ('Official GWR/RegBL record for a building') keyed on the federal EGID, and enumerates the fields contained in the record. The explicit pointer to reverse_geocode as the source of the EGID distinguishes it from the address-based siblings without requiring the schema to be opened.

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 usage path: obtain the EGID from reverse_geocode first, then call this tool. It does not state exclusions or what to do when an EGID is unknown/invalid, but the single-path workflow is unambiguous for a one-parameter lookup.

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

Deploy Server

Other Tools