Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
mike_model_infoA

Open a MIKE+ .sqlite model and report the active simulation/scenario/model, unit system, the list of simulation setups (msm_Project), scenarios, and element counts (nodes/links/catchments). Read-only. Needs MIKE+ + license.

mike_get_valuesA

Read parameter values from a MIKE+ table (e.g. msm_Link, msm_Node, msm_Catchment) for the given columns and optional element MUIDs. Read-only. Needs MIKE+ + license. Use this to identify current parameter values.

mike_set_valuesA

Set parameter values in a MIKE+ table for specific element MUIDs (e.g. change a pipe Diameter or Manning roughness). Returns before/after for the affected rows. MUTATES the database — ALWAYS use a copy. Needs MIKE+ + license. Pass 'muids' to scope the change; set all=true only when you intend to change every row.

mike_plot_rain_flowA

Render a stacked two-panel rainfall-runoff figure (rain inverted on top, flow on bottom) in the house style. Flow comes from a .res1d element; rainfall optional from a .dfs0. No license needed.

mike_plot_timeseriesB

Render a single-panel time-series plot (a quantity at an element) in the house style. No license needed.

mike_plot_networkA

Render a network layout map of a MIKE+ model from a .res1d — reaches/pipes as lines, nodes as points, equal-aspect, house style. Good for an overview figure. No license needed.

mike_results_listA

List what is inside a MIKE+ .res1d: quantities (WaterLevel/Discharge/...), element counts (nodes/reaches/structures/catchments) with sample ids, and the time range. No license needed.

mike_results_summaryA

Per-quantity peak summary (peak value, element, chainage, time) from a MIKE+ .res1d. No license needed. NOTE: this is the GLOBAL max over the whole run, which can fall in the warm-up/initial-condition period (a base-flow value near t=0) rather than the storm peak — pass skip_hours to exclude an initial window and always check peak_time.

mike_results_readB

Extract one time series (a quantity at an element) from a MIKE+ .res1d as times+values (downsampled to max_points). No license needed.

mike_runA

Run a MIKE+ simulation headless via the MIKE 1D engine. Runs the model's active simulation unless 'simulation' is given. Returns the result file paths plus the engine log tail. Needs MIKE+ installed + a valid license. ALWAYS run on a COPY of the model (mikeplus has no undo).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: reading/setting parameters, model info, three plot types, results listing/reading/summary, and simulation execution. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent 'mike_verb_noun' pattern (e.g., get_values, plot_network, results_list). The verbs are descriptive and uniformly formatted.

Tool Count5/5

10 tools is well within the ideal 3-15 range. The number covers the essential operations for MIKE+ modeling without being excessive.

Completeness4/5

The toolset covers the core workflow: model info, parameter read/write, simulation run, and results analysis/plotting. Minor gaps include lack of tools for structural model editing or scenario management, but for the intended purpose it is solid.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive