Skip to main content
Glama

FSI Channel Pressure

fsi_channel_pressure
Read-only

Computes plane-Poiseuille wall pressure drop for laminar flow between parallel plates, supplying the fluid pressure load and Reynolds-number validity check for FSI plate and interface simulations.

Instructions

Fully-developed plane-channel pressure drop Δp = 12·μ·U·L/h² (NO solver) — the fluid load that physically sources the pressure-loaded-plate FSI anchor. For laminar flow between parallel plates a gap gap_mm apart with mean velocity velocity_m_s over length length_mm, the exact plane-Poiseuille wall pressure drop feeds fsi_plate_deflection/fsi_interface_balance as pressure_pa. The Reynolds number Re = ρ·U·h/μ flags when the laminar (exact) assumption holds (Re ≲ 1400). Default fluid is water at 20 °C (μ=1e-3 Pa·s, ρ=1000).

Returns {pressure_pa, pressure_drop_pa, reynolds, regime, velocity_m_s, wall_shear_pa, fidelity, valid_range_ok, warnings, 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": {
      "velocity_m_s": "<velocity_m_s>",
      "length_mm": "<length_mm>",
      "gap_mm": "<gap_mm>"
    },
    "name": "fsi_channel_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
gap_mmYes
mu_pa_sNo
length_mmYes
rho_kg_m3No
workspaceNoRun this call in this named workspace
velocity_m_sYes

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds substantive context beyond that: it is analytic ('NO solver'), has a validity window, returns warnings/valid_range_ok, and can escalate — exactly the behavioral traits an agent needs.

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 formula and the 'NO solver' distinction are front-loaded, and the return-field list is compact. It is a dense block rather than scannable prose, and the parenthetical about the anchor tool is slightly verbose, but no sentence is wasted.

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 correctly enumerates the returned fields and flags the validity/escalation path, which is what an agent needs to interpret results. The only gap is that the `workspace` parameter's effect on execution is not addressed.

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 17% (just `workspace`), so the description must carry the load — and it does, tying gap_mm, velocity_m_s and length_mm to their physical roles and explaining that mu_pa_s/rho_kg_m3 default to water at 20 °C. Only the `workspace` parameter and the precise boundary conditions (unit conventions) remain unexplained.

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 names a specific computation (plane-Poiseuille channel pressure drop) and gives the exact closed-form expression, so an agent knows precisely what is produced. It also distinguishes itself from the FSI siblings by stating that its output is the *input* pressure for fsi_plate_deflection/fsi_interface_balance.

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 states the physical regime where the tool applies (laminar, Re ≲ 1400) and names the downstream tools to feed the result into, which is actionable routing guidance. It stops short of an explicit 'do not use if Re > 1400, use X instead' fallback, leaving the agent to infer the alternative from `escalate_to`.

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