Skip to main content
Glama

Thermal Transient 1D

thermal_transient_1d
Read-only

Compute analytic 1-D plane-wall transient temperatures using a one-term Heisler series, returning center and surface values for cooling or heating with surface convection.

Instructions

Analytic 1-D plane-wall transient conduction (one-term Heisler series), valid for Fourier ≳ 0.2 — the closed-form transient the Elmer thermal_transient solve is gated against, and the distributed (spatial-gradient) answer the lumped screen only approximates. A wall of half-thickness L cools/heats toward ambient by surface convection: Bi = h·L/k, Fo = α·t/L², α = k/(ρ·cₚ). Pass alpha_m2_s, or k+rho+cp, or a material (Materials DB: thermal_conductivity/Density/specific_heat); get h_conv from the h_estimate correlation screen rather than guessing.

As Bi→0 the body is isothermal and this collapses to the lumped exponential exp(−t/τ) (cross-checked via t_center_lumped_c / lumped_agrees). Returns {biot, fourier, eigenvalue_1, c1, t_center_c, t_surface_c, t_center_lumped_c, time_constant_s, one_term_valid, lumped_agrees}.

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": {
      "half_thickness_mm": "<half_thickness_mm>",
      "h_conv": "<h_conv>",
      "duration_s": "<duration_s>"
    },
    "name": "thermal_transient_1d"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
cpNo
rhoNo
h_convYes
materialNo
workspaceNoRun this call in this named workspace
alpha_m2_sNo
duration_sYes
t_ambient_cNo
t_initial_cNo
half_thickness_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.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 real substance beyond that — the validity limit of the one-term series, the returned fields including a self-check pair (one_term_valid, lumped_agrees), and the asymptotic Bi→0 collapse used as a cross-check. It does not say whether out-of-range Fo produces an error or a flagged-but-computed result, which is the one behavioral question left open.

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?

Two dense paragraphs, front-loaded with the method and its validity domain, then the parameter-derivation guidance, then the return keys. Almost every clause carries information; the Bi→0 cross-check sentence is the only part that edges toward elaboration, though it does justify the lumped_agrees return field.

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?

For an 11-parameter tool with near-zero schema descriptions and no output schema, the description supplies the method, the validity gate, parameter alternatives, sibling routing and the full return key list — enough to invoke it correctly. The gaps are the two temperature boundary-condition parameters and the workspace parameter, whose semantics are left entirely to their titles.

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?

With only 9% schema description coverage across 11 parameters, the description must carry the load, and it does for the physics-critical ones: three interchangeable ways to supply diffusivity (alpha_m2_s, k+rho+cp, or a material name with the Materials DB fields), the definition of L as half-thickness, t as duration, and the instruction to source h_conv from h_estimate. It leaves t_initial_c, t_ambient_c and workspace undocumented in both schema and description.

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 method and resource: 'Analytic 1-D plane-wall transient conduction (one-term Heisler series)' with the governing parameters Bi, Fo and α spelled out. It also positions itself against two named alternatives (the Elmer thermal_transient solve and the lumped screen), so an agent can tell exactly what computation this performs.

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 an explicit validity window ('valid for Fourier ≳ 0.2') and routes the agent to siblings: the Elmer thermal_transient solve for the gated case, the lumped screen for the approximate case, and h_estimate for h_conv ('rather than guessing'). Slightly short of 5 because the sibling references are informal ('the lumped screen', 'thermal_transient solve') rather than exact tool names like thermal_lumped / thermal_transient_submit, and it never says what to do if Fo < 0.2.

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