Skip to main content
Glama

Export Site Context

export_site_context
Read-onlyIdempotent

Purpose: retrieve source geometry and prepare a portable site-context file. When to use: when the user wants OpenStreetMap buildings, roads, water, green space and land use worldwide or available UK flood/heritage geometry around a location for QGIS, Rhino or CAD. Returns: actual GeoJSON, SVG or 2D DXF file contents, or a ZIP containing all three from one retrieval, source preview, per-layer coverage, and a companion manifest with CRS, local origin, attribution and limitations. DXF is local WGS84 UTM metres, not longitude/latitude; polygon holes are separate closed polylines. Limitations: community OSM geometry is not a survey; no inferred heights, terrain, DWG, 3D or desktop execution; basemap geometry is generalized and clipped to the request area; other sources retain touching features by default; an optional supplied outline can clip geometry with explicit omissions and an original-source audit companion. England flood checks the address point, not all nearby polygons. Missing layers remain explicit and can produce a partial export. Parameter guidance: supply address including city/country, prior site_ref, or user-supplied coordinates {lat,lng} with country_code. Coordinate mode does not verify the address or planning jurisdiction and only retrieves regional context. Pass a two-letter country code for non-UK address lookup and every supplied point (for example in, us, fr, au), selected layers, format and optional 250–1000m radius/title. Do not treat missing geometry as a clear planning result. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

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": {
      "layers": "<layers>",
      "format": "<format>"
    },
    "name": "export_site_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
formatYes
layersYes
addressNoSite address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations.
boundaryNoUser-supplied simple WGS84 outline inside the search radius. Selects whole touching features by default; boundary_mode clip intersects geometry. Does not verify ownership. No holes or self-intersections.
site_refNoCanonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted.
coordinatesNoUser-supplied WGS84 point. Provide an explicit country_code; omit site_ref. No address lookup or jurisdiction verification is performed.
country_codeNoISO two-letter country code. Required for non-UK addresses and all supplied coordinates; defaults to gb only for legacy address calls. Preserve the returned site_ref country.
boundary_modeNoDefaults to retaining whole touching features. clip intersects geometry with the supplied outline; requires boundary. Planar WGS84, not a legal boundary/survey or completeness check.
diagram_styleNoSVG display preset only; exported CAD/GIS geometry is unchanged. Figure-ground preserves courtyard holes; street diagram shows sampled road geometry, not routing.
radius_metersNoSearch radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected.

Output Schema

NameRequiredDescriptionDefault
queryNo
statusYes
detailsNo
messageNo
sourcesYes
headlineYes
site_refYes
retryableNo
error_codeNo
atlasly_linkYes
error_sourceNo
human_messageNo
key_data_pointsYes
top_constraintsYes
confidence_notesYes
executive_summaryYes
next_best_actionsYes
top_opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Site address or postcode, with town and country outside the UK. Alternatively pass site_ref from an earlier result; do not send both for different locations."
    • addedInput schema / properties / radius_meters / description
      Added value: +"Search radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover safety/idempotency (readOnly, idempotent, openWorld, non-destructive), and the description adds substantive behavior: DXF is local WGS84 UTM metres not lat/lng, polygon holes become separate polylines, missing layers yield an explicit partial export, the supplied outline can trigger clipping with omissions plus an original-source audit companion, and England flood checks only the address point.

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?

Front-loaded and labeled (Purpose / When to use / Returns / Limitations / Parameter guidance / Chaining), which makes a long block scannable despite 11 parameters. Some content restates schema constraints (radius range, country_code pattern) and the Returns sentence partially duplicates the output schema, so it is dense rather than perfectly trimmed.

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 complex, nested-object, 11-parameter export tool this covers retrieval scope, output formats and units, clipping behavior, partial-export semantics, chaining via site_ref, and explicit limitations. An agent can call it correctly and interpret results without further inference.

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 73%, so most parameters are documented structurally, but the description adds non-obvious semantics: country_code is mandatory for non-UK addresses and every supplied point, address+site_ref should not be sent for different locations, and radius is 250-1000m. It still does not explain diagram_style or boundary_mode beyond what the schema already says.

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?

Opens with an explicit verb+resource: 'retrieve source geometry and prepare a portable site-context file', then names the data domains (OSM buildings, roads, water, green space, land use; UK flood/heritage) and target consumers (QGIS, Rhino, CAD). It does not name or contrast the nearest siblings (export_site_boundary, generate_site_map), which is what separates a 5 from a 4 here.

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?

Explicit 'When to use' clause plus a negative guardrail ('Do not treat missing geometry as a clear planning result') and clear routing among the three input modes (address, site_ref, coordinates+country_code), including which mode skips verification. It stops short of naming an alternative tool or stating when to prefer export_site_boundary or generate_site_map instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources