Skip to main content
Glama

run_m03_sediment_morpho_sesc

Module 03: 2D Grid-RUSLE erosion, Wu (2007) sediment morphodynamics & PACl+PAM HESB sizing.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing: no mention that an upload_id from upload_terrain_base64 is needed, no runtime/cost expectations, no auth or quota implications, and no explanation of how no_dosing changes the run. Naming two published methods is not behavioral context.

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?

It is a single sentence with no padding, but brevity here reflects under-specification rather than economy. The sentence is front-loaded with an unexpanded module label instead of the actionable information 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 11-parameter simulation tool with no annotations and no output schema, the definition supplies no dependencies, no return-value expectations, and no guidance on defaults like the 178 mm rainfall or 50-year return period. It is far short of what is needed to invoke the tool correctly.

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?

With 11 parameters and only 45% schema description coverage, the description must compensate, and it adds nothing about any parameter. Key inputs such as storm_pattern, return_period, scenario, no_dosing and upload_id receive no meaning beyond their bare names.

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

Purpose2/5

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

The text is essentially a restatement of the tool name with expanded jargon: module number, '2D Grid-RUSLE erosion', 'Wu (2007) sediment morphodynamics' and 'PACl+PAM HESB sizing'. It never states the operational action (runs a sediment/erosion simulation over an uploaded terrain) or what it produces, so an agent knows the domain but not what calling it does.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as run_2d_flood_simulation or run_m02_coupled_swe_modflow6. The only implicit signal is the 'm03' module number in the name, which the description does not explain.

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