Skip to main content
Glama

site_reconstruction

Read-only

A dated, georeferenced 3D model of a site (entity_type + id, or lat + lng) with measurements: extent, elevation, slope, pits and heaps with volumes. The tier (lidar_2m or dem_30m) is decided before any charge. Slow (about 15–60 s). Agent keys only. Metered: see CHARGING in the server instructions; quote first with billing_quote.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "site_reconstruction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe entity's numeric id (with entity_type).
latNoLatitude in decimal degrees, -90 to 90 (WGS84).
lngNoLongitude in decimal degrees, -180 to 180 (WGS84).
as_ofNoPick the lidar collection and texture nearest this date, YYYY-MM-DD.
radius_mNoHalf the square's side, in metres, 100-1000. Default 300.
entity_typeNoEntity kind: deposit | infrastructure | company | project. With id; or pass lat + lng.
include_modelNoAlso return the binary glTF model as model_glb_base64 (a lidar model is about 5 MB as base64).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • removedInput schema / properties / as_of / default
      Removed value: -null
    • removedInput schema / properties / as_of / title
      Removed value: -"As Of"
    • removedInput schema / properties / entity_type / default
      Removed value: -null
    • removedInput schema / properties / entity_type / title
      Removed value: -"Entity Type"
    • removedInput schema / properties / id / default
      Removed value: -null
    • removedInput schema / properties / id / title
      Removed value: -"Id"
    • changedInput schema / properties / include_model / description
      Previous value: -"Also return the binary glTF model as model_glb_base64 (a lidar model is about 5 MB as base64). Default false: the card only."New value: +"Also return the binary glTF model as model_glb_base64 (a lidar model is about 5 MB as base64)."
    • removedInput schema / properties / include_model / title
      Removed value: -"Include Model"
    • removedInput schema / properties / lat / default
      Removed value: -null
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / lng / default
      Removed value: -null
    • removedInput schema / properties / lng / title
      Removed value: -"Lng"
    • removedInput schema / properties / radius_m / default
      Removed value: -null
    • removedInput schema / properties / radius_m / title
      Removed value: -"Radius M"
    • removedInput schema / title
      Removed value: -"site_reconstructionArguments"
    • removedOutput schema / title
      Removed value: -"site_reconstructionDictOutput"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed7 schema fields changed
    • addedInput schema / properties / as_of / description
      Added value: +"Pick the lidar collection and texture nearest this date, YYYY-MM-DD."
    • addedInput schema / properties / entity_type / description
      Added value: +"Entity kind: deposit | infrastructure | company | project. With id; or pass lat + lng."
    • addedInput schema / properties / id / description
      Added value: +"The entity's numeric id (with entity_type)."
    • addedInput schema / properties / include_model / description
      Added value: +"Also return the binary glTF model as model_glb_base64 (a lidar model is about 5 MB as base64). Default false: the card only."
    • addedInput schema / properties / lat / description
      Added value: +"Latitude in decimal degrees, -90 to 90 (WGS84)."
    • addedInput schema / properties / lng / description
      Added value: +"Longitude in decimal degrees, -180 to 180 (WGS84)."
    • addedInput schema / properties / radius_m / description
      Added value: +"Half the square's side, in metres, 100-1000. Default 300."
  4. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description layers on the details an agent actually needs: metered billing via server CHARGING, a quote-before-charge step, the pre-charge tier decision (lidar_2m vs dem_30m), agent-key auth requirement, and a 15–60 s latency warning. This is exactly the extra behavioral context annotations cannot carry.

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-loads the deliverable, then terse clauses on tier, latency, auth, and billing, with the quote-first routing at the end. Dense and largely waste-free, though the telegraphic style ('Agent keys only') is slightly compressed versus plain prose.

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 metered, slow, open-world read tool with a full schema and an output schema, the description covers cost, latency, auth, tier behavior, and both input modes. Error semantics and partial-failure behavior for the binary model are not addressed, which is the only remaining gap.

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 every parameter including include_model's ~5 MB base64 note is already documented in the schema, so baseline 3 applies. The description only restates the two addressing modes and the tier names; it adds no format or default detail beyond the schema.

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?

States a concrete resource and modality: a dated, georeferenced 3D site model with terrain measurements (extent, elevation, slope, pits, heaps with volumes). The input-mode disjunction (entity_type + id, or lat + lng) further pins down what it produces. It does not name a sibling such as look_at or deposit_brief to differentiate, so it stops short of a 5.

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 explicit operational guidance: quote first with `billing_quote`, tier is decided before any charge, agent keys only, expect 15–60 s. It never states when-not to use it or names the sibling that handles a nearby need, so no true alternatives routing.

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