Skip to main content
Glama

DEM Flow Submit

dem_flow_submit

Submit a YADE discrete-element simulation of sphere discharge from a flat-bottomed hopper to measure steady mass-flow rate and validate the Beverloo outflow exponent.

Instructions

Discharge spheres from a flat-bottomed hopper box through a central orifice with the REAL YADE discrete-element engine and measure the steady mass-flow rate — gated against granular_screen('beverloo') (flow ∝ outlet^2.5). Submit two outlet_m sizes and feed the (outlet, flow) pair to granular_screen('beverloo_exponent') to check the Beverloo 2.5 exponent (vs the Torricelli 2.0 of a draining fluid). YADE is GPL-3.0 and is run ONLY in a subprocess; runs OFF the MCP channel via a background job.

box_m is the [Lx, Ly, Lz] hopper box (m; default [0.10, 0.10, 0.20]); outlet_m the central orifice diameter; settle_steps/flow_steps the DEM step budgets. Returns {job_id, status, cache_hit, oracle}; the job result carries the Beverloo oracle PLUS {mass_flow_kg_s, n_discharged, discharge_time_s, positions:[...]}. Absent YADE: {ok:false, reason, install, oracle}.

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": "dem_flow_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
box_mNo
densityNo
outlet_mNo
radius_mNo
young_paNo
n_spheresNo
workspaceNoRun this call in this named workspace
flow_stepsNo
friction_degNo
settle_stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With annotations declaring readOnlyHint=false, destructiveHint=false, and openWorldHint=false, the description adds meaningful operational context: YADE is GPL-3.0, runs only in a subprocess, executes off the MCP channel as a background job, and returns a structured fallback {ok:false, reason, install, oracle} when YADE is absent. It does not cover polling or concurrency behavior, but the core behavioral envelope is well disclosed.

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 front-loaded with the main purpose and workflow, and most sentences carry useful operational detail. It is dense but not padded; the GPL/subprocess/fallback details and return-shape note earn their place, though the paragraph could be split for easier scanning.

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

Completeness3/5

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

For a complex 10-parameter DEM submission with no output schema, the description covers the return shape ({job_id, status, cache_hit, oracle}) and missing-YADE fallback, which is valuable. It still leaves five material parameters unexplained and does not mention how to retrieve the background job result, so an agent must infer the polling path from sibling tools like job_status/job_result.

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

Parameters3/5

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

Schema description coverage is only 10%, so the description must compensate. It explains box_m as [Lx, Ly, Lz] with a default, outlet_m as central orifice diameter, and settle_steps/flow_steps as DEM step budgets. However, density, radius_m, young_pa, n_spheres, and friction_deg are left completely undocumented in both the schema and the description.

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 states a specific verb and resource: discharge spheres from a flat-bottomed hopper through a central orifice using the REAL YADE DEM engine and measure steady mass-flow rate. It explicitly distinguishes this from the sibling granular_screen by framing the result as gated against granular_screen('beverloo') and meant to feed granular_screen('beverloo_exponent').

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

Usage Guidelines5/5

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

It gives an explicit workflow: submit two outlet_m sizes, then feed the (outlet, flow) pair to granular_screen('beverloo_exponent') to check the Beverloo 2.5 exponent. It also names the analytic alternative granular_screen('beverloo'), so the agent knows when to use the numerical DEM path versus the screen.

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

Deploy Server

Other Tools