Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

FSI Interface Balance

fsi_interface_balance
Read-only

Check force conservation across a fluid-solid coupling interface by comparing fluid pressure load with solid reaction; returns residual and balance status.

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}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
width_mmYes
length_mmYes
pressure_paYes
fluid_force_nNo
solid_reaction_nNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description aligns by stating 'NO solver' and 'returns the reference analytic load'. It adds useful behavioral context: the computation is analytic, the residual formula is given, and the no-input fallback behavior is disclosed. It does not detail every output field's meaning, but the core behavior is transparent.

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 well-organized: it front-loads the core purpose, then explains the physics, the optional inputs, and the fallback behavior. The output list is compact. It could be slightly shorter, but every sentence earns its place.

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 a read-only analytic check with 5 parameters and no output schema, the description covers the essential context: what the tool computes, how the residual is defined, what inputs are optional, and what the return object contains. It does not explain the meaning of every output field (e.g., fidelity, escalate_to), but the core usage is complete.

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 0%, so the description must compensate. It explains the physical meaning of pressure_pa, length_mm, width_mm (uniform pressure over a strip, F = pressure·area), and clarifies the optional fluid_force_n and solid_reaction_n inputs. This adds real semantic value beyond the bare schema.

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: it performs a partitioned wet-interface force balance, computing a reference analytic load and comparing supplied fluid/solid forces. It also distinguishes itself from a solver and names its FSI analogue (optics energy-balance gate), making its role clear among many FSI 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?

The description explains when to use it: to check conservation across a partitioned FSI coupling surface, and it clarifies the optional inputs (fluid_force_n and/or solid_reaction_n) and the no-input case. It does not explicitly name alternative tools or state when not to use it, but the context is clear enough for an agent to select it appropriately.

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