Server Details
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Hydrata/hydrata-mcp-server
- GitHub Stars
- 0
See and control every tool call
Available Tools
9 toolscancel_runTry in Inspector
Cancel an in-flight simulation run.
Works on runs in built, queued, or computing status. Cleans up compute resources (terminates EC2 instance, Celery task, or Batch job).
Returns 409 if the run is already in a terminal state (complete, cancelled, or error).
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The run ID to cancel |
get_projectTry in Inspector
Get details of a specific ANUGA project including its scenarios.
Returns the project name, projection (EPSG code), base map ID, and configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | The project ID |
get_runTry in Inspector
Get full details of a simulation run including timing and results.
Returns the complete run record: status, progress, timing (start/end timestamps, duration), compute details (backend, instance type, cost), mesh info, error messages, and result log. Use get_run_status for lightweight polling; use this for final results.
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The run ID |
get_run_statusTry in Inspector
Lightweight status check for a simulation run (fast, <50ms).
Use this for polling instead of get_run. Returns only: id, status, progress_pct (0-100), eta_seconds, error_message, and compute_backend.
Poll every 5-10 seconds. Terminal states: complete, error, cancelled.
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The run ID |
get_scenarioTry in Inspector
Get scenario details including its current status and latest run.
The status field is computed from the latest run and will be one of: created, building, built, queued, computing, processing, complete, error, or cancelled. A scenario must be in 'built' status before it can be run.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | The project ID | |
| scenario_id | Yes | The scenario ID |
list_projectsTry in Inspector
List ANUGA simulation projects accessible to the authenticated user.
Returns a paginated list of projects with their names, projections, and base map references.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default 1) | |
| page_size | No | Results per page, max 100 (default 100) |
list_runsTry in Inspector
List all simulation runs across all scenarios in a project.
Returns a paginated list of runs. Optionally filter by status to find active, completed, or failed runs.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default 1) | |
| page_size | No | Results per page, max 100 (default 100) | |
| project_id | Yes | The project ID | |
| status_filter | No | Filter by status: created, building, built, queued, computing, processing, complete, error, cancelled. Omit for all. |
retry_runTry in Inspector
Retry a failed simulation run.
Resets an errored run back to 'created' status and triggers a new package build. The same run ID is reused. Only valid when status is 'error'. Returns 409 for any other state.
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The run ID to retry |
start_simulationTry in Inspector
Start a flood simulation run for a built scenario.
The scenario must be in 'built' status. Returns 202 with the new run. The run transitions through: built → queued → computing → processing → complete.
After starting, poll get_run_status to track progress. Returns 409 if the scenario is not in the correct state.
| Name | Required | Description | Default |
|---|---|---|---|
| scenario_id | Yes | The scenario ID to run | |
| compute_backend | No | Compute backend: 'local' (Celery), 'ec2' (dedicated instance), or 'batch' (AWS Batch spot, cheapest). Default: 'local' | local |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.