Skip to main content
Glama

The New Engineer — HVAC

size_expansion_vessel

Read-onlyIdempotent

Size the expansion vessel and pressurisation of a closed heating or chilled-water circuit to EN 12828: static height, minimum pressure p0, fill pressure pa, final pressure pe, expansion volume, water reserve, nominal vessel volume with the standard vessel to buy, safety valve setting together with the minimum it must not fall below, pressure class of the lowest equipment, intermediate vessel when needed.

Heights become pressures through the real density of the fluid, at the temperature that matters for each: the coldest for p0, the design temperature for the valve and the lowest point. Water and glycols therefore give different figures for the same height.

Use it whenever the user asks to size or check an expansion vessel, pressurisation unit, pre-charge pressure or safety valve — in any language: vase d'expansion, maintien de pression, Ausdehnungsgefäss, Druckhaltung, vaso di espansione, vaso de expansión.

Needs the installation water volume and THREE heights, all measured from the point where the expansion vessel connects to the network:

  • the highest point of the installation, above it;

  • the lowest point, usually below it (negative) or level with it;

  • the safety valve, which always sits on the heat generator or chiller. If the user does not know it, it is assumed 1 m above the vessel connection, and the result says so. Ask the user for the volume and the three heights before calling. NEVER invent a height: if the lowest point or the valve height is unknown, omit it. The result is then marked provisional and lists the questions to ask. Build your answer on answer_outline: it carries the assumptions, the questions and the link to the website, which measures all of these on the user's IFC model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fluidNoHeat-transfer fluid: 'eau' (Water), 'meg' (MEG), 'mpg' (MPG), 'tyfocor' (TYFOCOR L (MPG)). Omit: plain water.
languageNoThe user's language, for labels and alerts.en
glycol_pctNoGlycol concentration in %, ignored for water. Defaults to 30 %.
installationNo'chauffage' for heating, 'refroidissement' for cooling / chilled water. Omit: heating.
pressurisationNoType of pressurisation: 'statique' (Pressure-maintained by gas cushion (Statico)), 'compresseur' (Compressor-driven (Compresso)), 'pompe' (Pump-driven (Transfero)). Omit: gas-cushion vessel.
flow_temperature_cNoFlow temperature, °C. Omit: 80 in heating, 6 in cooling.
design_temperature_cNoHottest the fluid ever gets, standstill included. Omit: the warmer of flow and return in heating, 40 °C in cooling.
return_temperature_cNoReturn temperature, °C. Omit: 60 in heating, 12 in cooling.
filling_temperature_cNoTemperature at which the circuit is filled, °C. Omit: 10.
installation_volume_lYesTotal water content of the closed circuit, in litres: pipes, emitters, generator, buffer tank.
lowest_point_from_unit_mNoHeight of the REAL lowest point of the installation - the lowest drain - relative to the point where the expansion vessel connects to the network, in metres. NEGATIVE when below it, 0 when the vessel connects at the lowest point. Taken as given: no margin is added. Ask the user. NEVER invent it: if the user has not given it, omit it - the result is then marked provisional and returns the question to ask.
safety_valve_from_unit_mNoHeight of the safety valve relative to the point where the expansion vessel connects to the network, in metres. The safety valve always sits on the heat generator (boiler, heat pump) or chiller - tell the user so, it helps them find it. Ask for it; if they cannot say, omit it: it is then assumed 1 m above the vessel connection, and the result says so.
safety_valve_setting_barNoSafety valve setting in bar, one of the standard settings. Omit to take the smallest standard setting that works here. A setting below the minimum the installation needs is raised, and the result says so.
highest_point_above_unit_mYesHeight of the REAL highest point of the installation - the top air vent - above the point where the expansion vessel connects to the network, in metres. Taken as given: no margin is added.
minimum_required_pressure_barNoPressure the installation requires at the pressurisation unit whatever the height - against cavitation at a pump suction, for instance. p0 never falls below it. Omit: zero.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description goes far beyond this: it explains the conversion of heights to pressures via real fluid density, the no-margin treatment of heights, the default 1 m assumption for the safety valve when unknown, and the rule "NEVER invent a height: if the lowest point or the valve height is unknown, omit it. The result is then marked provisional and lists the questions to ask." This gives the agent clear expectations about outputs and assumptions.

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 longer than the average but well structured: purpose first, then the height-pressure principle, a clear usage trigger, a bulleted list of required heights, and a final imperative about not inventing values. Each sentence carries information needed to call the tool correctly, with minimal redundancy. The translated terms list is slightly long but useful for multilingual user requests.

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

Completeness5/5

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

Given the tool's 15 parameters and rich input schema, the description covers all critical context: what to ask the user, how to handle unknown heights, the assumption behavior, and the need to build the answer on `answer_outline`. It also accounts for provisional results and how the website measures heights on an IFC model. The output schema exists, so return-value details are not required in the description.

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

Parameters4/5

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

The input schema already has 100% parameter description coverage, so the baseline is 3. The description adds meaning beyond the schema by explaining the common reference point for all heights ("the point where the expansion vessel connects to the network") and the omission behavior for unknown heights. It also connects fluid choice to pressure differences ("Water and glycols therefore give different figures for the same height"), which reinforces parameter semantics.

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 opens with a specific verb and resource: "Size the expansion vessel and pressurisation of a closed heating or chilled-water circuit to EN 12828," then enumerates the concrete outputs (static height, p0, pa, pe, expansion volume, nominal vessel volume, valve setting, etc.). This clearly distinguishes it from the sibling tools, which concern refrigerant zones and Swiss refrigerant checks, even though it does not name them.

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?

The description explicitly states when to use the tool: "Use it whenever the user asks to size or check an expansion vessel, pressurisation unit, pre-charge pressure or safety valve — in any language," and lists translations. It also gives pre-call guidance: "Ask the user for the volume and the three heights before calling." It does not explicitly mention sibling alternatives or exclusions, but the domain is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources