Skip to main content
Glama

Thermal Lumped

thermal_lumped
Read-only

Estimate transient component warm-up without meshing: calculate temperature rise, time constant, steady-state percentage, and radiation flags from mass, power, convection, and area inputs.

Instructions

Lumped first-order transient warm-up (no mesh). ΔT_ss = P/(h·A), τ = m·c_p/(h·A), T(t) = T_amb + ΔT_ss·(1−e^(−t/τ)). c_p is an explicit value/quantity-string ('900 J/kg/K') or read from material. Get h_conv from the h_estimate correlation screen rather than guessing. With duration_s the temperature + fraction-of-steady reached are returned. A radiation screen flags when the steady-state radiative HTC exceeds h_conv. Returns {t_ambient_c, delta_t_steady_k, t_steady_c, time_constant_s, t_final_c, reached_steady_pct, h_rad_w_m2k, radiation_significant}.

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": {
      "mass_g": "<mass_g>",
      "power_w": "<power_w>",
      "h_conv": "<h_conv>",
      "area_mm2": "<area_mm2>"
    },
    "name": "thermal_lumped"
  }
}

Input Schema

NameRequiredDescriptionDefault
c_pNo
h_convYes
mass_gYes
power_wYes
area_mm2Yes
materialNo
workspaceNoRun this call in this named workspace
duration_sNo
emissivityNo
t_ambient_cNo

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 safety is covered; the description adds real behavioral content beyond that — the closed-form model used, the fact that a radiation screen runs and flags when radiative HTC exceeds h_conv, and an explicit list of returned fields. It does not discuss validity limits (Biot number) of the lumped assumption, which would be the remaining high-value disclosure.

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-loads the model and equations, then parameter sourcing, then outputs — a sensible order for a physics tool. Dense but every clause carries information; the return-field enumeration is long but substitutes for the absent output schema, so it earns its space.

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?

With 10 parameters, 10% schema coverage and no output schema, the description fills both gaps: it explains parameter sourcing and enumerates all eight returned fields. An agent can construct a correct call and interpret the response 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 10%, so the description must compensate, and it largely does: c_p's accepted formats (number or '900 J/kg/K' string) and its fallback to `material`, h_conv's recommended source, and duration_s's effect on the result are all explained. The remaining inputs (mass_g, power_w, area_mm2, emissivity, t_ambient_c) are only documented implicitly through the formulas ΔT_ss = P/(h·A) and τ = m·c_p/(h·A), which an agent can decode but which are not stated in prose.

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 analysis type (lumped first-order transient warm-up) with the governing equations and explicitly notes '(no mesh)', which separates it from the meshed siblings thermal_transient_1d and thermal_transient_submit. An agent knows exactly what physics this tool performs without opening the schema.

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?

Gives concrete prerequisites rather than just context: c_p must be supplied explicitly as a value/quantity-string or sourced from `material`, and h_conv should come from the `h_estimate` correlation screen 'rather than guessing' — a named alternative. It also says what duration_s unlocks. It stops short of stating when to prefer this over thermal_transient_1d or thermal_radiation_submit, so it is not a full when/when-not rubric.

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