Skip to main content
Glama

Thermal Composite Wall

thermal_composite_wall
Read-only

Calculate exact thermal resistance, overall U-value, heat flux, and interface temperatures for a plane composite wall using layer thicknesses, conductivities, and optional convection coefficients.

Instructions

Exact series thermal-resistance network of a plane composite wall (NO solver) — the classic overall-U calculation and the conjugate-heat-transfer family's closed-form oracle. layers is the in→out list of solid layers, each {thickness_mm, k | material} (k in W/m·K, or a Materials-DB name); h_in/h_out are optional convection film coefficients (W/m²K). Per unit area R = 1/h_in + Σ tᵢ/kᵢ + 1/h_out, U = 1/R, q = U·(t_in − t_out), and every surface/interface temperature follows exactly.

Returns {u_w_m2k, r_total_m2k_w, q_w_m2, q_w, layer_resistances_m2k_w, interface_temps_c (inner surface → outer surface), t_in_c, t_out_c, area_m2}.

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": {
      "layers": "<layers>",
      "t_in_c": "<t_in_c>",
      "t_out_c": "<t_out_c>"
    },
    "name": "thermal_composite_wall"
  }
}

Input Schema

NameRequiredDescriptionDefault
h_inNo
h_outNo
layersYes
t_in_cYes
area_m2No
t_out_cYes
workspaceNoRun this call in this named workspace

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.4/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 meaningful context beyond that: the exact resistance network used, that results are per unit area, and that a Materials-DB lookup is allowed for k. It does not explicitly bound the model (steady-state, 1-D series, no radiation/contact resistance), which is the one behavioral caveat an engineer would want.

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 identity and scope, then the formulas, then return fields — a sensible information hierarchy. It is dense and formula-laden, and the stray punctuation in '(NO solver)' plus the varied naming of the query sections adds a little friction, but no sentence is padding.

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?

There is no output schema, and the description fully enumerates the returned keys (u_w_m2k, r_total_m2k_w, q_w_m2, q_w, layer_resistances_m2k_w, interface_temps_c, t_in_c, t_out_c, area_m2). Combined with the assembled formulas, an agent has everything needed to call and interpret the tool.

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 14%, so the description must carry the load, and it largely does: `layers` is documented as an ordered in→out list of {thickness_mm, k | material} with units, and h_in/h_out are defined as optional film coefficients in W/m²K. `area_m2` and `workspace` are left unmentioned (area only appears implicitly in the return list), so compensation is strong but not complete.

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 (exact series thermal-resistance network of a plane composite wall) with the key qualifier 'NO solver' that separates it from the FEM/transient siblings (thermal_transient_1d, thermal_lumped, fem_thermal_results, cht_*_submit). The parenthetical 'classic overall-U calculation and the conjugate-heat-transfer family's closed-form oracle' makes the identity unambiguous.

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 'NO solver' / 'closed-form oracle' framing tells the agent this is the fast analytic path rather than a mesh-based analysis, which implicitly routes it away from the fem_* and *_submit tools. It never names a specific alternative tool or states an explicit when-not condition (e.g., transient, radiation, 2-D effects), so it stops short of full routing guidance.

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