Skip to main content
Glama

CFD Body Drag

cfd_body_drag
Read-only

Estimate external-flow drag for spheres, cylinders, and bluff shapes analytically to screen designs before running a wind-tunnel CFD solve.

Instructions

Analytic EXTERNAL-flow drag screen (NO solver, milliseconds) — the external twin of cfd_pipe_flow, and the banded oracle the wind-tunnel solve cfd_external_flow_submit(model=…) is checked against. Use this FIRST to narrow a design space; escalate to the solve only for the shapes that survive.

Three families:

  • shape='sphere' — Clift–Gauvin over the whole standard drag curve, Cd = 24/Re·(1+0.15·Re^0.687) + 0.42/(1+4.25e4·Re^-1.16). Collapses to the EXACT Stokes 24/Re as Re→0; valid to Re=2e5 (it does not model the drag crisis). Pass diameter_mm + velocity_m_s.

  • shape='cylinder' — Sucker–Brauer crossflow Cd (axis ⟂ flow), Cd ≈ 10 at Re=1, 1.45 at Re=100, 1.2 at Re=1e5. Pass diameter_mm, velocity_m_s, optional length_mm (default 1 m, i.e. drag per unit span; L/D<10 warns about end relief).

  • a tabulated bluff/streamlined shape — 'cube_face_on', 'flat_plate_normal', 'hemisphere_open_back', 'streamlined_body', 'car_modern', … (shape='list' returns the whole table). Needs frontal_area_mm2 (or a model handle, whose silhouette along flow_direction is measured off the live solid) + velocity_m_s; cd overrides the table with a known value.

Fidelity: sphere/cylinder are correlations with band_pct 10/15; the table is band_pct 20 and only valid for Re ≈ 1e4–1e6 on a shape that genuinely matches.

Returns {cd, drag_force_n, frontal_area_m2, dynamic_pressure_pa, velocity_m_s, fidelity, band_pct, escalate_to} plus {reynolds, regime, valid_range_ok, warnings} for sphere/cylinder — or {shapes: {name: cd}} for shape='list'.

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

Input Schema

NameRequiredDescriptionDefault
cdNo
fluidNoair-20c
modelNo
shapeNosphere
mu_pa_sNo
length_mmNo
rho_kg_m3No
workspaceNoRun this call in this named workspace
diameter_mmNo
velocity_m_sNo
flow_directionNo
frontal_area_mm2No
stl_tolerance_mmNo

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

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

Annotations only say readOnly/openWorld=false; the description adds critical behavior: no solver, milliseconds, fidelity band_pct per family, the Re 1e4–1e6 validity window for the table, that the sphere correlation does not model the drag crisis, and that L/D<10 triggers an end-relief warning. This is exactly the kind of context annotations cannot carry.

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?

Front-loaded with the key distinction and structured into families, so it scans well despite length. The embedded formulas are long but earn their place by defining which correlation applies at which Re.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the return fields including the shape='list' variant, and it covers the zero-required-params puzzle by specifying per-family inputs. What an agent needs to call it correctly is present.

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 coverage is only 8% with 13 params, so the description must compensate and largely does — it ties shape families to required params (diameter_mm/velocity_m_s, length_mm default 1 m, frontal_area_mm2 or model+flow_direction, cd override). However fluid, mu_pa_s, rho_kg_m3, and stl_tolerance_mm are never explained, leaving a real gap.

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?

States a specific verb+resource (analytic external-flow drag screen) and immediately distinguishes it from siblings: the 'external twin of cfd_pipe_flow' and the pre-screen oracle for cfd_external_flow_submit. An agent can tell exactly which of the several cfd_* tools this is without opening a schema.

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?

Explicit routing: 'Use this FIRST to narrow a design space; escalate to the solve only for the shapes that survive.' Names the alternative (cfd_external_flow_submit) and the condition selecting it, plus which params switch between the three shape families.

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