Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_hvac_manual_j_solver

Calculates ACCA Manual J whole-building heating and cooling loads, including peak heat loss, sensible/latent cooling gain, and heat pump tonnage sizing from floor area and design temperatures.

Instructions

ACCA Manual J whole-building heating and cooling load calculation. Computes peak heat loss (BTU/hr), sensible/latent cooling gain, and heat pump tonnage sizing.

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": {
      "floor_area_sqft": "<floor_area_sqft>",
      "winter_design_temp_f": "<winter_design_temp_f>"
    },
    "name": "omni_hvac_manual_j_solver"
  }
}

Input Schema

NameRequiredDescriptionDefault
floor_area_sqftYesTotal conditioned floor area in square feet
insulation_gradeNoaverage_code
ceiling_height_ftNoAverage ceiling height in feet
summer_design_temp_fNoOutdoor 1% summer dry-bulb design temperature in °F
winter_design_temp_fYesOutdoor 99% winter dry-bulb design temperature in °F
indoor_cooling_setpoint_fNo
indoor_heating_setpoint_fNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose output quantities (peak heat loss, sensible/latent gain, tonnage), but omits that this is a reduced-input approximation of Manual J — real Manual J requires envelope, glazing and orientation data that this 7-parameter schema cannot express — and says nothing about assumptions, accuracy limits, or error behavior.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the standard and method, then the returned quantities. No filler or repetition.

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?

No output schema exists, and the description does a fair job naming return quantities, but for a 7-parameter engineering calculation it leaves default behavior, setpoint units/semantics, and the simplified-model caveat unaddressed. Adequate to select the tool, thin for invoking it confidently.

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 coverage is 57%: floor_area_sqft, ceiling_height_ft, summer_design_temp_f and winter_design_temp_f are documented, while indoor_heating_setpoint_f and indoor_cooling_setpoint_f have no description anywhere. The description adds no parameter meaning at all — it never mentions inputs, defaults, or which two are required — so it does not compensate for the gap.

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?

Names a specific standard (ACCA Manual J) plus a concrete verb-resource pair ('whole-building heating and cooling load calculation') and enumerates the computed quantities. No sibling in the list (octagon, regular polygon, SEPP 72-T, universal query) overlaps this domain, so the agent can identify it unambiguously.

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?

Usage is only implied by the purpose statement — there is no explicit when-to-use, no note on prerequisites (e.g. that design temperatures come from ASHRAE 99%/1% tables), and no statement about when a different approach is needed. An agent can infer the intended scenario but gets no routing rules.

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