Skip to main content
Glama

Summarize buildings

summarize_buildings
Read-onlyIdempotent

Summarize building footprints within a radius of any location: returns count, total and mean footprint area, height/floor coverage, and top building types.

Instructions

Summarize building footprints in an area: count, footprint area, height/floor coverage, mix.

From Overture's buildings theme (issue #23). Returns count,
total/mean footprint area in m^2, height_known_pct/num_floors_known_pct
(height and floor count are sparse in real Overture data — this reports
coverage rather than pretending every building has a value, with
mean_height_m/mean_num_floors alongside when any are known), and
top_subtypes/top_classes (top 10 each by count). Returns a structured
{"error": ...} if upstream is unavailable or the dataset is missing
geometry/bbox.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYes
lonYes
radius_mNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.1/5.0
Behavior5/5

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

The description goes beyond the read-only/idempotent annotations by explaining data sparsity behavior: it reports height_known_pct/num_floors_known_pct as coverage rather than assuming complete data, and includes mean values only when any are known. It also discloses error behavior (structured {"error": ...}) for upstream unavailability or missing geometry/bbox.

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?

The description opens with a one-sentence summary of purpose and metrics, then adds necessary detail about data provenance, coverage semantics, and error handling. Every sentence contributes new information and is clearly structured without redundancy.

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 read-only summary tool with an output schema, the description covers data provenance, output metrics, sparse-data handling, and error responses. It does not explain input parameters or contrast with sibling tools, leaving some context incomplete, but the essential operational details are present.

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

Parameters2/5

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

The schema has zero descriptions for lat, lon, and radius_m, and the description does not compensate by defining these parameters or their units. It only says 'in an area', which implies a spatial scope but does not specify the role of each parameter or the meaning of radius_m.

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 states a specific verb ('Summarize'), a specific resource ('building footprints in an area'), and the exact metrics returned (count, footprint area, height/floor coverage, mix). It clearly distinguishes this from sibling tools like `buildings_at` (likely raw building access) and `summarize_area` (broader area summaries) by narrowing to building footprints.

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?

The description implies its use case through the word 'Summarize' and building-specific focus, but it does not explicitly state when to choose this tool over siblings like `buildings_at` or `summarize_area`. No exclusions or alternatives are mentioned, so usage guidance is only implied, not explicit.

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

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/chuofringer/placeroot'

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