Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

oven_heat_load

Calculates steady-state cure-oven heat load by balancing product, hanger, chain, exhaust, and wall losses to size burner capacity and account for design margin and efficiency.

Instructions

Steady-state cure-oven heat balance: product + hangers + chain + exhaust + wall losses.

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": {
      "parts_per_hour": "<parts_per_hour>",
      "part_weight_lb": "<part_weight_lb>",
      "cure_metal_temp_f": "<cure_metal_temp_f>",
      "oven_air_temp_f": "<oven_air_temp_f>",
      "entering_temp_f": "<entering_temp_f>",
      "ambient_temp_f": "<ambient_temp_f>",
      "envelope_area_ft2": "<envelope_area_ft2>",
      "wall_u_btuh_ft2_f": "<wall_u_btuh_ft2_f>",
      "exhaust_scfm": "<exhaust_scfm>",
      "design_margin": "<design_margin>",
      "burner_efficiency": "<burner_efficiency>"
    },
    "name": "oven_heat_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
exhaust_scfmYes
design_marginYes1.0 = no margin.
part_materialNosteel
ambient_temp_fYes
line_speed_fpmNo
part_weight_lbYes
parts_per_hourYes
entering_temp_fYes
oven_air_temp_fYes
hanger_weight_lbNo
burner_efficiencyYes
cure_metal_temp_fYes
envelope_area_ft2Yes
wall_u_btuh_ft2_fYes
chain_weight_lb_per_ftNo

Output Schema

NameRequiredDescriptionDefault
total_kwYes
warningsNo
chain_btuhYes
total_btuhYes
walls_btuhYes
assumptionsNo
exhaust_btuhYes
hangers_btuhYes
product_btuhYes
design_marginYes
subtotal_btuhYes
burner_input_kwYes
oven_air_temp_cYes
burner_efficiencyYes
burner_input_btuhYes
cure_metal_temp_cYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the steady-state modeling assumption, which is genuinely useful, but says nothing about unit conventions, validity constraints on the 11 required inputs, what the returned heat-load figure represents, or how design_margin and burner_efficiency alter the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted words, which is structurally clean. However, the brevity reflects under-specification rather than disciplined editing for a 15-parameter engineering calculation.

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?

An output schema exists, so return values need not be explained and the steady-state framing is stated. Against 15 parameters at 7% description coverage and zero annotations, though, the definition leaves too much for an agent to infer about units, assumptions, and term-by-term inputs.

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% across 15 parameters, so the description must compensate and largely fails. The enumerated terms loosely map to part_weight_lb, hanger_weight_lb, chain_weight_lb_per_ft, exhaust_scfm, and envelope_area_ft2/wall_u_btuh_ft2_f, but temperatures, line_speed_fpm, part_material, design_margin, and burner_efficiency get no shared meaning added.

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 phrase 'Steady-state cure-oven heat balance' names a specific calculation and the enumerated terms (product, hangers, chain, exhaust, wall losses) tell the agent exactly what is summed. It stops short of a verb and offers no differentiation from siblings such as oven_dwell_check or hook_load_check, so an agent must infer that this one sizes the burner/heat load.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisite context (e.g. 'call after oven_dwell_check to size the burner'), and no exclusion of when this tool is the wrong choice. Only the words 'cure-oven heat balance' imply a usage context, which the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.