Skip to main content
Glama

CHT Graetz Submit

cht_graetz_submit
Destructive

Submit an asynchronous Elmer flow-coupled Graetz channel simulation to validate the true Nusselt number with a computed laminar profile and return a job ID for polling.

Instructions

Flow-coupled Graetz channel via Elmer (SIMULATION_NEXT B4), asynchronous — the TRUE Nusselt validation that upgrades cht_channel_submit's plug flow: FlowSolve computes the real laminar profile and HeatSolver rides on it (Convection = Computed) between two isothermal walls. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising.

Two gates: the solved parabola's u_max/u_mean ≡ 3/2 exactly, and the developed mixing-cup decay d ln(T_wall−T_bulk)/dx fitted over the second half of the channel yields Nu, gated against the Graetz eigenvalue Nu_T = 7.5407 (parallel plates, constant wall temperature) — a slug profile would give π² = 9.87, so the gate also proves the profile coupling is real. This closes the loop with the h_estimate correlation screen. The writer polices Re < 400, development lengths inside the first 45 %, and cell Péclet ≤ 25. Also accepts a prepared case_dir.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, u_max_over_mean (≈1.5), nu_fit, nu_exact, nu_ratio (≈1, ±10 %), nu_slug, reynolds, prandtl, 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_graetz_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nxNo
nyNo
sifNocase.sif
gap_mNo
t_in_cNo
k_fluidNo
case_dirNo
cp_fluidNo
length_mNo
mu_fluidNo
t_wall_cNo
rho_fluidNo
workspaceNoRun this call in this named workspace
velocity_m_sNo

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.1/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that the tool is asynchronous, returns a degradation dict rather than raising when ElmerSolver is missing, enforces three validation gates, and returns a job id that must be polled via job_result. This is exactly the operational context an agent needs for a write/submit tool.

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?

The description is dense but front-loads the core purpose and then layers in gates, prerequisites, and return behavior. Given the complexity of the simulation, most sentences earn their place, though some gate detail could be tightened without losing meaning.

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 a complex 14-parameter simulation tool with no output schema, the description does well on operational behavior, failure modes, and return fields including nu_ratio and job polling. The main gap is that it does not document most input parameters, though all are optional with defaults, so an agent can still invoke it.

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

Parameters2/5

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

Schema description coverage is only 7%, so the description must carry the burden for 14 parameters. It only explicitly mentions 'case_dir' and does not explain what nx, ny, sif, gap_m, length_m, velocity_m_s, or the fluid properties control, nor their units or interactions. The physical context is rich but parameter-level guidance is largely absent.

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?

The description states a specific verb and resource: a flow-coupled Graetz channel simulation via Elmer, asynchronous, performing a 'TRUE Nusselt validation.' It explicitly distinguishes itself from the sibling cht_channel_submit by saying it upgrades that tool's plug-flow model, so an agent can identify its role 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?

It clearly positions the tool relative to cht_channel_submit and h_estimate, and states the ElmerSolver prerequisite plus the degradation behavior when it is absent. However, it does not give an explicit 'use this instead of X when...' decision rule or list exclusions, leaving some routing inference to the agent.

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