Skip to main content
Glama

run_2d_flood_simulation

Module 01: 2D Full-Momentum SWE flood routing, hydraulic structures & Design Rev 5 earthworks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_2d_flood_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idNo
has_damNo
api_tokenNoOptional GLBH-* Bearer token
module_idNom01
site_nameNoProject site name for engineering reports
upload_idNoUpload ID up_xxxx returned by upload_terrain_base64
inflow_m3sNo
guest_tokenNoOptional anonymous session guest token
rainfall_mmNo
duration_minNo
return_periodNo
storm_patternNoalternating_block
white_label_companyNoCustom company branding (Team subscribers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool mutates data, runs synchronously or asynchronously, consumes quota, requires authentication, or has side effects; it only names the simulation model and module.

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

Conciseness2/5

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

The description is a single noun phrase rather than a structured, front-loaded explanation. Though short, it is under-specified for a 13-parameter simulation tool, so brevity comes at the cost of clarity.

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

Completeness1/5

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

For a complex simulation tool with 13 parameters, no annotations, no output schema, and low schema coverage, the description is completely inadequate. It provides no operational context, prerequisites, or return-value expectations.

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

Parameters1/5

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

The input schema has 13 parameters with only 38% description coverage, and the description adds no meaning for any parameter such as case_id, inflow_m3s, rainfall_mm, storm_pattern, or has_dam. It does not compensate for the low schema coverage.

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

Purpose3/5

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

The description identifies the module (Module 01) and the technical domain (2D full-momentum SWE flood routing, hydraulic structures, Design Rev 5 earthworks), which distinguishes it somewhat from sibling modules. However, it is a label-like fragment with no explicit action verb, so it never directly states that the tool runs a simulation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as run_m00_globalgeo_crs_mesh, run_m02_coupled_swe_modflow6, or upload_terrain_base64. It also omits prerequisites like required uploads or tokens, leaving the agent to infer usage from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources