Skip to main content
Glama

FSI Pressure Plate Submit

fsi_pressure_plate_submit

Submits an asynchronous partitioned fluid-structure interaction solve using preCICE, OpenFOAM, and CalculiX for a clamped flexible plate, returning a job ID to poll for tip displacement and convergence.

Instructions

Partitioned fluid-structure-interaction solve on the preCICE OpenFOAM↔ CalculiX stack, asynchronous (OFF the MCP channel) — the real coupled-field twin of the analytic fsi_plate_deflection / fsi_interface_balance oracles. A flexible flap clamped at a channel floor deflects under the flow: OpenFOAM (pimpleFoam) writes the wet-interface Force, ccx_preCICE returns the Displacement, and preCICE drives the implicit coupling to convergence each time window. preCICE is LGPL-3.0 and the two heavy solvers run ONLY as subprocesses; degrades to {ok:false, reason, install, stack} when the stack is absent (build via scripts/install-solvers.sh fsi).

Physics knobs: inlet_velocity_m_s, nu_m2_s, rho_kg_m3 (fluid), youngs_pa/poisson/density_kg_m3 (solid), end_time_s/time_window_s/ max_iterations (coupling). Geometry/mesh come from the validated vendored template (no FreeCAD touch). Returns the degradation dict, or {job_id, status, cache_hit}; poll job_result for {ok, time_windows, tip_disp_m, tip_history, coupling_converged, case_dir} — the tip displacement is the field the fsi_plate_deflection oracle gates.

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

Input Schema

NameRequiredDescriptionDefault
nu_m2_sNo
poissonNo
timeoutNo
rho_kg_m3No
workspaceNoRun this call in this named workspace
youngs_paNo
end_time_sNo
density_kg_m3No
time_window_sNo
max_iterationsNo
inlet_velocity_m_sNo

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.5/5.0
Behavior5/5

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

Annotations already mark the tool as not read-only, not destructive, and closed-world, but the description adds substantial behavioral detail beyond them: it runs off the MCP channel, uses two heavy solver subprocesses, relies on LGPL-3.0 preCICE, degrades to a structured `{ok:false, reason, install, stack}` response, and returns `{job_id, status, cache_hit}` for polling. This is rich operational context for a complex async submit tool.

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 definition is front-loaded with the core purpose and async behavior, then moves into dependencies, degradation, parameters, and return/polling details. It is dense and somewhat long, but the complexity justifies most of the content and little is redundant.

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?

For an 11-parameter async solver submit tool with no output schema, the description explains the return object and how to poll `job_result` for `tip_disp_m`, `coupling_converged`, and related outputs. It also covers stack absence and geometry/mesh sourcing. The main remaining gap is that `timeout` behavior is not described.

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?

Schema description coverage is only 9%, so the description must compensate. It does so by naming and grouping most parameters into fluid (`inlet_velocity_m_s`, `nu_m2_s`, `rho_kg_m3`), solid (`youngs_pa`, `poisson`, `density_kg_m3`), and coupling (`end_time_s`, `time_window_s`, `max_iterations`) roles. `timeout` is not explained, and `workspace` is only covered by the schema, which keeps this below a 5.

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 action and resource: submit a partitioned fluid-structure-interaction solve on a preCICE OpenFOAM↔CalculiX stack. It explicitly distinguishes this real coupled-field job from the analytic `fsi_plate_deflection` / `fsi_interface_balance` oracles, so an agent can identify its role without inspecting siblings.

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

Usage Guidelines4/5

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

It explains the asynchronous workflow: submit here, then poll `job_result` for coupled results. It also names the analytic oracle alternatives and indicates degradation when the solver stack is absent. It stops short of an explicit when-to-use-this-vs-sibling rule, but the context is clear.

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