France Geodata

Fr Buildings Near

fr_buildings_near

Read-onlyIdempotent

Buildings within a radius (max 500 m) of a point in France, from the IGN BD TOPO building layer. Each building has GeoJSON polygon geometry, height (m), floors, dwellings, use, nature and construction dates. Reports the total matched and flags truncation. Use for "buildings within 200 m of X" and GeoJSON export of them.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": 45.764,
      "lon": 4.8357,
      "limit": 10,
      "radius_m": 200
    },
    "name": "fr_buildings_near"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Latitude (WGS84), e.g. 45.764.
`lon`	Yes	Longitude (WGS84), e.g. 4.8357.
`limit`	No	Max buildings returned, 1-200 (default 50). Nearest first.
`radius_m`	No	Search radius in metres, 1-500 (default 200).
`include_geometry`	No	Include polygon geometry (default true). Set false for attributes only.

Output Schema

Name	Required	Description	Default
`note`	No
`found`	No
`center`	No
`source`	No
`radius_m`	No
`returned`	No
`buildings`	No
`truncated`	No
`total_matched`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered; the description adds non-obvious behavior beyond them — the hard 500 m radius ceiling, that results report a total matched count, and that truncation is explicitly flagged. It doesn't discuss rate limits or ordering beyond the schema's "nearest first".

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?

Front-loaded with the operation and scope, then attribute list, then output behavior, then canonical use case. Every sentence carries distinct information with no repetition of the tool name or filler.

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?

For a read-only lookup with a full output schema, the description covers source, coordinate scope, return attributes, truncation semantics and a canonical use case — nothing an agent needs to invoke it correctly 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 description coverage is 100%, so ranges and defaults are already documented per parameter. The description only reinforces the 500 m radius cap and the geometry-vs-attributes distinction, adding little beyond the schema.

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 verb+resource (buildings within a radius of a point), constrains geography (France) and names the upstream data source (IGN BD TOPO building layer), plus enumerates the returned attributes. An agent can distinguish it from generic siblings like search_within without opening the schema.

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 concrete usage pattern ("buildings within 200 m of X" and GeoJSON export), which tells the agent which intent maps here. It does not name an alternative tool or state when-not to use it, so it stops short of full routing guidance.

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

All France Geodata tools Inspect

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.