Skip to main content
Glama

FSI Interface Balance

fsi_interface_balance
Read-only

Compute the reference wet-interface load (pressure × area) and check fluid force against solid reaction to quantify FSI coupling conservation error.

Instructions

Partitioned wet-interface force balance (NO solver) — the FSI analogue of the optics energy-balance gate. The fluid presses a uniform pressure_pa over the length_mm×width_mm strip, so the total traction is F = pressure·area; a converged partitioned solve must hand the solid exactly this load and the solid's support reactions must carry it (Newton's third law across the coupling surface). Pass the measured fluid_force_n (∮p·dA over the OpenFOAM wet patch) and/or solid_reaction_n (Σ ccx reaction at the clamp); the relative residual |F_fluid − R_solid|/F_fluid is the conservation error. With neither supplied it returns the reference analytic load (residual 0) the real solve closes on.

Returns {area_mm2, reference_load_n, fluid_force_n, solid_reaction_n, residual_n, relative_residual, balanced, fidelity, escalate_to}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pressure_pa": "<pressure_pa>",
      "length_mm": "<length_mm>",
      "width_mm": "<width_mm>"
    },
    "name": "fsi_interface_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
width_mmYes
length_mmYes
workspaceNoRun this call in this named workspace
pressure_paYes
fluid_force_nNo
solid_reaction_nNo

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

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

Beyond the readOnly/openWorld annotations, it discloses key behavior: no solver runs, the reference load is analytic, the residual formula is |F_fluid − R_solid|/F_fluid, and the tool returns a zero-residual reference case when no measurements are given. It also explains the physical conservation principle being checked.

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 dense but front-loads the core concept and stays focused on computation and interpretation. It is longer than typical, but the length is justified by the formulas and return fields; minor symbolic notation could be trimmed.

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?

With no output schema, the description lists the returned fields and explains the central residual. It leaves the meanings of balanced, fidelity, and escalate_to implicit, which are important for interpreting the gate result, so it is strong but not fully complete.

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

Parameters5/5

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

Schema description coverage is low at 17%, but the description compensates by defining the core parameters in physical terms: pressure over a length×width strip, fluid force as the integral over the wet patch, and solid reaction as the sum of clamp reactions. The only parameter not described here, workspace, already has a schema 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 precise resource and operation: a partitioned wet-interface force balance that acts as a conservation gate without running a solver. It distinguishes itself from the FSI solver siblings by explicitly saying 'NO solver' and by explaining that it checks the load handoff against Newton's third law.

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 clearly describes when to supply measured fluid force and/or solid reaction, and what happens when neither is supplied (it returns the reference analytic load). However, it does not explicitly name alternative sibling tools or state when not to use this check versus running a full FSI solve.

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