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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
swmm_runA

Run swmm5 on an INP and write rpt/out + manifest.json into runDir. When 'node' is omitted the runner resolves 'auto' after the run: the outfall carrying the largest total volume in the Outfall Loading Summary (else the first [OUTFALLS] entry), so the manifest's peak metric targets the outfall that matters.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 4 tools

Disambiguation4/5

The four tools have mostly distinct purposes: running a simulation, parsing peak flow, parsing continuity tables, and comparing continuity between two reports. The only mild overlap is between swmm_continuity and swmm_compare, since both concern continuity, but their descriptions clearly distinguish single-file parsing from two-file comparison.

Naming Consistency4/5

All tools share the swmm_ prefix and use lowercase snake_case, giving a predictable namespace. The only minor inconsistency is grammatical form: swmm_peak and swmm_continuity are nouns while swmm_compare and swmm_run are verbs, though the names remain clear and readable.

Tool Count4/5

Four tools is a small but reasonable set for a focused SWMM workflow, and each tool serves a clear role in running or evaluating a model. It is slightly narrow, but not so thin that the surface feels incomplete for the stated purpose.

Completeness3/5

The surface covers the core run-and-check workflow: execute SWMM, extract peak flow, inspect continuity, and compare continuity across reports. However, it lacks tools for other common report outputs such as outfall loading summaries, node/link summaries, flooding, or reading the generated manifest, leaving notable gaps for broader model evaluation.

Maintenance

ActivityActive
ResponsivenessSyncing