Skip to main content
Glama

CHT Channel Submit

cht_channel_submit
Destructive

Submits an asynchronous conjugate heat transfer solve coupling a fluid channel to a conducting solid wall, returning a job ID for result polling or an install/degradation report.

Instructions

Conjugate heat transfer via Elmer (P3 M6 frontier), asynchronous — ONE solve spanning a plug-flow fluid channel AND a conducting solid wall coupled at their shared interface. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising.

Builds the two-body channel (constant outer flux_w_m2, inlet Dirichlet t_in_c, all else adiabatic) whose gates are exact WITHOUT a Nusselt correlation: the outlet bulk temperature follows the energy balance q″·L = ṁ·c_p·ΔT and the solid-layer drop is q″·t/k. Defaults are the live-validated water channel (cell Péclet ≈ 9 — the builder rejects > 25, where stabilized advection visibly leaks the energy balance). Also accepts a prepared case_dir.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, t_outlet_mean_c, t_out_exact_c, energy_balance_ratio (≈1, ±3%), dt_solid_k, dt_solid_exact_k, solid_drop_ratio (≈1), pe_cell, case_dir}.

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

Input Schema

NameRequiredDescriptionDefault
nxNo
sifNocase.sif
t_in_cNo
k_fluidNo
k_solidNo
case_dirNo
cp_fluidNo
length_mNo
ny_fluidNo
ny_solidNo
flux_w_m2No
rho_fluidNo
workspaceNoRun this call in this named workspace
velocity_m_sNo
fluid_height_mNo
solid_thickness_mNo

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

A3.6/5.0
Behavior4/5

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

Annotations only declare destructive/open-world/read-only flags; the description adds the async contract (returns {job_id, status, cache_hit}, poll job_result), the degradation-not-exception error path, the solver dependency, and the acceptance tolerances (±3% energy balance). The one unstated risk is that destructiveHint=true is never explained — nothing says whether passing an existing case_dir overwrites it.

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?

Purpose and the async/error contract are front-loaded in the first sentences, and the trailing sentence usefully summarizes the return payload. The middle paragraph's justification of why the energy gates are exact is longer than an agent strictly needs to pick the tool, but it is dense rather than padded.

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

Completeness3/5

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

For an async, no-output-schema, 16-parameter submission tool, the description does cover the return shape and the failure mode, so an agent knows what happens after the call. It is still incomplete on the mesh/grid parameters and on the `sif` file input, which nothing in the schema explains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 6% across 16 parameters, so the description carries most of the burden. It does give physical meaning to the key inputs (outer flux_w_m2, inlet Dirichlet t_in_c, case_dir) and supplies the governing relations q″·L = ṁ·c_p·ΔT and q″·t/k, but nx, ny_fluid, ny_solid, sif, and the geometry params remain unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific physics and scope: a coupled conjugate heat transfer solve over a plug-flow fluid channel plus a conducting solid wall, run asynchronously via Elmer. It is far more than a restatement of the title, but it never explicitly contrasts itself with the adjacent siblings that sound closest (cht_graetz_submit, fsi_channel_pressure, fem_run_submit).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real preconditions (requires ElmerSolver; when absent it returns {ok:false, reason, install} rather than raising) and a hard validity boundary (Péclet > 25 is rejected by the builder). What it never states is when to reach for this versus cht_graetz_submit or the generic fem_run_submit; the 'exact WITHOUT a Nusselt correlation' line implies a contrast but does not spell it out.

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