Skip to main content
Glama

Hydrata - ANUGA Flood Simulation

Wait for a terrain import

get_terrain
Read-onlyIdempotent

Poll a terrain's import until it is ready (or error), bounded by timeout_seconds.

Returns outcome — exactly one of ready, error, timed_out, not_found (the project has no terrain yet; an unknown terrain_id is an API 404 error instead) — plus the last status seen (creating → styling → ready | error) and phase (that status, or not_found; never empty), polls, elapsed_seconds and the full terrain record (its gn_layer is the published elevation dataset pk once ready). An import takes minutes to tens of minutes (the SAME 32 MB 1 m DEM measured 4.5 min once and 26 min once — the worker's S3 download speed dominates), so timed_out is normal and NOT a failure: keep calling with the same arguments while status is still creating/styling; several calls in a row is expected. error is terminal — the import failed and no default input rows were seeded; upload a corrected GeoTIFF as a new terrain.

ready is written by the import task; the project's default input rows (Boundary 01, Friction 01, Inflow 01, Rainfall 01, Building 01, MeshRegion 01, one GeoNode layer each) are seeded by the NEXT task in the chain and appear over the following ~30 s. Poll the input-layer list until it is non-empty before attaching your own layer to a default row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe project ID
terrain_idNoThe terrain ID from finalize_terrain_upload. Omit to follow the project's newest terrain.
timeout_secondsNoHow long this call keeps polling before it returns `timed_out` (default 240, ceiling 280 — the prod /mcp/ proxy cuts a call at 300 s). 0 = one status read, no waiting.
poll_interval_secondsNoSeconds between polls (default 5)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties
      Removed value: -{
      -  "result": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.