Skip to main content
Glama
Sign In

baseray

by ai.baseray
OverviewDiscussionsAdmin

Find the building at an address

find_buildings
Read-onlyIdempotent

Looks up the building at one specific address, point (latitude and longitude) or company registration number (with its country). Use for one known location; it does not search or count buildings across an area. Takes exactly one of address, latitude+longitude, or companyRegistrationNumber+country. The nearest building comes in full in buildings: its address and postcode (and whether the address is an address record, a business listing or only the nearest road), use, footprint, floor area, height, floors, volume, dwellings, entrances, statedFacts (what its record states: construction year, floors, areas, units, declared use and more, where known), flood zone, seismic risk and the earthquakes on record nearby, solar potential, whether solar panels are already on the roof (from a register of solar installations at the address, with their power and battery storage, or a dated photo), and the businesses registered at the address with their largest stated size and turnover. Each figure carries its basis: measured, stated or estimated. The other buildings found there come in nearby as free previews (sizes as ranges, no house number, businesses or record), unless the workspace has already opened them. Cost: 1 credit to open the nearest building when the workspace has not opened it in the last year; previews are free.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many buildings to return, nearest first. Default 3.
addressNoA street address with the town, e.g. "Bulevardul Eroilor 10, Brașov".
countryNoCountry of the company registration number: RO, CZ or DK.
latitudeNoLatitude of the point, WGS84.
longitudeNoLongitude of the point, WGS84.
radiusMetersNoHow far from the point or address to look, in metres. Default 40.
companyRegistrationNumberNoA Romanian CUI (e.g. "RO14399840" or "14399840"), a Czech IČO (e.g. "00216305") or a Danish CVR number (eight digits, e.g. "24256790"); finds the building the business is registered at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / companyRegistrationNumber / description
      Previous value: -"A Romanian CUI (e.g. \"RO14399840\" or \"14399840\") or a Czech IČO (e.g. \"00216305\"); finds the building the business is registered at."New value: +"A Romanian CUI (e.g. \"RO14399840\" or \"14399840\"), a Czech IČO (e.g. \"00216305\") or a Danish CVR number (eight digits, e.g. \"24256790\"); finds the building the business is registered at."
    • changedInput schema / properties / country / description
      Previous value: -"Country of the company registration number: RO or CZ."New value: +"Country of the company registration number: RO, CZ or DK."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "RO",
-  "CZ"
-]New value: +[
+  "RO",
+  "CZ",
+  "DK"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"A street address in Romania or Czechia, with the town, e.g. \"Bulevardul Eroilor 10, Brașov\"."New value: +"A street address with the town, e.g. \"Bulevardul Eroilor 10, Brașov\"."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavior: the nearest building is returned in full, nearby buildings are free previews, and opening an unopened building costs 1 credit. It also explains the `basis` labeling for figures, which is valuable behavioral context.

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 purpose and key constraint are front-loaded, and the detailed return-value enumeration earns its place because there is no output schema. The paragraph is dense but organized, with only minor verbosity in the long list of returned fields.

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 7 parameters, full schema coverage, and no output schema, the description is complete: it covers input modes, return contents, preview behavior, and credit cost. An agent has enough information to choose and invoke the tool correctly.

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 100%, so parameter syntax is already well documented. The description adds meaningful invocation semantics not expressible in the schema: exactly one of address, latitude+longitude, or companyRegistrationNumber+country must be supplied.

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 gives a specific verb and resource: it looks up the building at one address, point, or company registration number. It explicitly scopes the tool to one known location and rules out area-wide search/count use, which distinguishes it from siblings such as search_buildings.

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?

It clearly says when to use this tool: for one known location, and explicitly says it does not search or count buildings across an area. It also states the mutually exclusive input modes, though it does not name the alternative sibling tool.

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

All baseray 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