Skip to main content
Glama

Heat Transfer Coefficient Estimate

h_estimate
Read-only

Estimate convection and radiation heat-transfer coefficients from geometry, temperature, and flow to provide thermal boundary values for lumped, transient, or convection analyses instead of guessing.

Instructions

Screening convection coefficient h (NO solver) — the honest h_conv to feed thermal_lumped / thermal_transient_1d / a convection BC, instead of a guess. geometry picks the correlation: natural (velocity_m_s = 0) 'vertical_plate' | 'horizontal_cylinder' (Churchill–Chu); forced (velocity_m_s > 0) 'flat_plate' (averaged laminar/mixed Nu) | 'cylinder_crossflow' (Hilpert). characteristic_mm is the plate height/length or cylinder diameter. Film-temp air properties built in; another fluid needs explicit k_w_mk + nu_m2_s + pr (+ beta_per_k for natural). emissivity > 0 adds the linearized radiation screen into h_total_w_m2k.

This is a focusing estimate, not a gate: fidelity='correlation' with band_pct the literature scatter (±15–20 %). Escalate to the conjugate solve cht_channel_submit (or a meshed convection BC via thermal_transient_submit) when the thermal margin is within ~2× band_pct. Returns {geometry, mode, correlation, h_conv_w_m2k, h_rad_w_m2k, h_total_w_m2k, nusselt, reynolds, rayleigh, prandtl, film_temp_c, fidelity, band_pct, 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": {
      "geometry": "<geometry>",
      "characteristic_mm": "<characteristic_mm>",
      "t_surface_c": "<t_surface_c>"
    },
    "name": "h_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
prNo
fluidNoair
k_w_mkNo
nu_m2_sNo
geometryYes
workspaceNoRun this call in this named workspace
beta_per_kNo
emissivityNo
t_ambient_cNo
t_surface_cYes
velocity_m_sNo
characteristic_mmYes

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
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that, adding real behavioral context: no solver is invoked, results carry fidelity='correlation' with ±15–20% literature scatter, valid_range_ok and warnings flags exist, and emissivity > 0 folds radiation into h_total. It stops short of stating validity-range failure behavior or units/normalization caveats in detail.

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 core claim and the 'NO solver' qualifier, then correlation mapping, then escalation guidance — a sensible order. It is dense and the trailing return-field enumeration runs long, but every clause carries decision-relevant information given there is no output schema.

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?

For a 12-parameter tool with no output schema, the description covers the correlation selection logic, fluid override requirements, radiation coupling, fidelity/scatter expectations, warning fields, and the full return payload. An agent could call this correctly and interpret the result without further documentation.

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 8%, so the description must compensate, and it largely does: it enumerates the four geometry values, defines characteristic_mm, explains that velocity_m_s = 0 means natural convection, and specifies that a non-air fluid requires explicit k_w_mk + nu_m2_s + pr (+ beta_per_k for natural) and that emissivity > 0 enables the radiation term. t_surface_c, t_ambient_c and workspace are left to the schema, which keeps this just below full credit.

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 and resource ('Screening convection coefficient h (NO solver)') and immediately distinguishes the tool from the solvers it coexists with by naming cht_channel_submit and thermal_transient_submit as escalation paths. An agent can tell what this computes and what it does not.

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 rules: geometry/velocity_m_s select the correlation (natural vs forced, plate vs cylinder), and escalation is conditioned quantitatively ('when the thermal margin is within ~2x band_pct'). Also names the downstream consumers (thermal_lumped, thermal_transient_1d, convection BC) it exists to feed.

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