Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

amu_sizing

Calculate make-up air unit CFM and burner input (BTU/h) from exhaust airflow, design outdoor and supply temperatures, elevation, and burner efficiency for paint-line ventilation sizing.

Instructions

Air make-up unit: make-up cfm and burner input, BTU/h = 1.08 × cfm × ΔT (standard air).

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": {
      "exhaust_cfm": "<exhaust_cfm>",
      "design_outdoor_temp_f": "<design_outdoor_temp_f>",
      "supply_temp_f": "<supply_temp_f>",
      "burner_efficiency": "<burner_efficiency>"
    },
    "name": "amu_sizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
burner_typeNodirect_fired
exhaust_cfmYes
elevation_ftNo
makeup_ratioNo
supply_temp_fYes
burner_efficiencyYes
gas_hhv_btu_per_scfNo
design_outdoor_temp_fYesSite winter heating design dry-bulb, °F.

Output Schema

NameRequiredDescriptionDefault
warningsNo
delta_t_cYes
delta_t_fYes
makeup_cfmYes
makeup_m3hYes
assumptionsNo
burner_typeYes
exhaust_cfmYes
gas_input_kwYes
makeup_ratioYes
density_ratioYes
gas_flow_scfhYes
supply_temp_fYes
gas_input_btuhYes
heat_output_kwYes
heat_output_btuhYes
burner_efficiencyYes
design_outdoor_temp_fYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the governing relationship (BTU/h = 1.08 × cfm × ΔT) and the standard-air basis, which is real behavioral context, but it says nothing about elevation correction, efficiency handling, or what the output schema returns beyond the two named quantities.

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?

One front-loaded sentence with no filler: the resource, the outputs, and the formula all appear immediately. It is efficient but so terse that concision shades into under-specification.

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

Completeness2/5

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

For an 8-parameter engineering tool with no annotations and 13% schema coverage, the description is too thin. It gives the core formula but leaves the roles of elevation, make-up ratio, burner type, efficiency, and gas HHV unexplained, which is material for correct invocation.

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 13% for 8 parameters. The description implies that exhaust_cfm drives make-up air and that ΔT derives from design_outdoor_temp_f and supply_temp_f, but makeup_ratio, elevation_ft, burner_type, burner_efficiency, and gas_hhv_btu_per_scf are never explained, leaving most parameters undocumented in both places.

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

Purpose3/5

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

The description identifies the resource (air make-up unit) and the two computed outputs (make-up cfm and burner input) and gives the governing BTU/h equation. However, the sizing verb is only implied through the equation, and nothing distinguishes it from siblings such as oven_heat_load or booth_exhaust_airflow.

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 statement of when to use this tool rather than related siblings, and no exclusions or prerequisites. An agent must infer from the context that this applies to make-up air sizing for exhaust-driven systems.

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