Skip to main content
Glama

create_pump_control_scenario

Apply a time-based pump on/off or speed schedule to a cloned water network and run a simulation to analyze hydraulic effects.

Instructions

Apply a time-based pump on/off or speed schedule and simulate.

A clone of the source network is created; the original is unchanged.

Each pump entry maps to a list of EPANET simple-control strings::

{
    "Pump9": [
        "LINK Pump9 1.0 AT TIME 06:00",
        "LINK Pump9 CLOSED AT TIME 22:00"
    ]
}

Args: network_id: Source network id. pump_schedule: {pump_id: [control_string, ...]} schedule. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
network_idYes
scenario_idNo
pump_scheduleYes
run_simulationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses key behavioral traits: it creates a clone of the source network, leaving the original unchanged. No annotations are provided, so the description carries the burden; it covers the important cloning behavior but does not detail other aspects like permissions or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose sentence, then details on cloning and parameter format. It is slightly lengthy due to the example, but every sentence adds value. The front-loaded purpose is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, nested objects, output schema exists), the description adequately covers cloning behavior, schedule format, simulation option, and parameter semantics. The return value is likely described in the output schema, so not needed here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds significant meaning: it explains the pump_schedule format with an example, clarifies network_id as source id, scenario_id as cloned session id, and defaults for run_simulation. This surpasses the baseline of 3 for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it applies a time-based pump schedule and simulates, using a specific verb-resource combination. It distinguishes from sibling tools like 'set_pump_speed' or 'create_valve_control_scenario' by focusing on pump scheduling and cloning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating pump schedules but does not explicitly state when to use this tool versus alternatives like 'set_pump_speed' or other scenario tools. No exclusions or context for when not to use are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Applied-Artificial-Intelligence-Eurecat/epanet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server