Agentic SWMM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| swmm_runA | Run swmm5 on an INP and write rpt/out + manifest.json into runDir. When 'node' is omitted, auto-detect the first entry of the .inp [OUTFALLS] section so the manifest's peak metric targets the real outfall. |
| swmm_peakC | Parse peak flow and time-of-peak for a specific node/outfall from a SWMM .rpt. The node name must be supplied (no default). |
| swmm_continuityC | Parse Runoff Quantity / Flow Routing continuity tables from a SWMM .rpt. |
| swmm_compareC | Compare continuity error (%) between two SWMM .rpt files (e.g., GUI vs CLI). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct SWMM task: comparing reports, parsing continuity tables, extracting peak flows, and running simulations. No overlap or confusion.
All tools follow a consistent 'swmm_<verb>' pattern, making them predictable and easy to differentiate.
Four tools is reasonable for a focused SWMM analysis server, covering key operations without unnecessary clutter.
Covers core workflows (run, compare, parse continuity and peaks). Minor gaps like editing input files or exporting results are acceptable for this scope.