Hydrata - ANUGA Flood Simulation

Register an uploaded terrain

finalize_terrain_upload

Step 2 of a terrain import: register the PUT GeoTIFF as a Terrain and start the import.

Call this only after the presigned PUT returned 200. Creates the Terrain row (status creating) and queues the import chain — reproject to UTM, publish the layer + hillshade, style — which also seeds the project's six default boundary, friction, inflow, rainfall, building and mesh-region rows. Returns 202 with the terrain record; keep its id for get_terrain. A 400 UPLOAD_NOT_FOUND means no object is at staging_key: the PUT did not land (check its status code and Content-Type) — do not retry finalize until it has.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Terrain title (default: the filename without .tif)
`process_id`	No	`process_id` returned by presign_terrain_upload (pass it so the upload's progress record is reused; the API tolerates its absence)
`project_id`	Yes	The project ID
`staging_key`	Yes	`staging_key` returned by presign_terrain_upload

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026
- removedOutput schema / properties
```
Removed value: -{
-  "result": {
-    "type": "string"
-  }
-}
```
- removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
- removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```
AddedSep 21, 2026

TDQS

Score is being calculated.

All Hydrata - ANUGA Flood Simulation 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.