Skip to main content
Glama

run_m02_coupled_swe_modflow6

Module 02: Coupled 2D SWE + 3D MODFLOW 6 DISV+XT3D groundwater seepage & piping.

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_m02_coupled_swe_modflow6"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenarioNolevee_piping
api_tokenNoOptional GLBH-* Bearer token
site_nameNoProject site name for engineering reports
upload_idNoUpload ID up_xxxx returned by upload_terrain_base64
guest_tokenNoOptional anonymous session guest token
return_periodNo
cutoff_depth_mNo
white_label_companyNoCustom company branding (Team subscribers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/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 identifies the coupled physics model, which adds some context beyond the schema, but says nothing about execution behavior, duration, asynchronous job handling, token requirements, or what the simulation returns.

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 fragment with no structure beyond a module label. It is concise only because it is under-specified; there is no front-loaded action statement or operational detail an agent needs.

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 an 8-parameter, multi-physics simulation tool with no annotations and no output schema, the description is grossly incomplete. It does not explain what the tool returns, how long it takes, what authentication is required, or how the parameters interact.

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

Parameters2/5

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

Schema description coverage is 63%, leaving several parameters such as scenario, return_period, and cutoff_depth_m undocumented in the schema. The description adds no meaning for any parameter; 'piping' loosely hints at the default scenario but does not explain how parameters shape the run.

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 names a specific coupled simulation domain (2D SWE + 3D MODFLOW 6 DISV+XT3D groundwater seepage & piping), which distinguishes it from sibling simulation tools. However, it is written as a label rather than a statement of action: there is no verb like 'run' or 'simulate', and no indication of what the tool actually produces.

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

Usage Guidelines1/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 siblings such as run_2d_flood_simulation or run_m03_sediment_morpho_sesc. It also does not mention prerequisites like uploading terrain data first via upload_terrain_base64, despite upload_id being a parameter.

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