{"data":{"name":"com.thenewengineer/hvac","title":"The New Engineer — HVAC","description":"IFC models: duct networks, circuits, pressure drop. EN 12828 vessels, EN 378, Swiss refrigerants.","version":"1.3.0","websiteUrl":"https://thenewengineer.com/ai","repositoryUrl":null,"remotes":[{"url":"https://thenewengineer.com/mcp","type":"streamable-http"}],"packages":[],"status":"active","isLatest":true,"publishedAt":"2026-10-10T15:34:24.120Z","updatedAt":"2026-10-10T15:34:24.120Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"stars":null,"title":"The New Engineer — HVAC","source":"official-registry","sourceId":"com.thenewengineer/hvac","updatedAt":"2026-10-10T15:34:24.120Z","confidence":100,"websiteUrl":"https://thenewengineer.com/ai","description":"IFC models: duct networks, circuits, pressure drop. EN 12828 vessels, EN 378, Swiss refrigerants.","verification":"official","repositoryUrl":null}],"toolIndex":{"tools":[{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"apply_ifc_rules","title":null,"description":"Turn what you read in the overview into rules the tool replays on\nEVERY piece of the model, including the ones you were never shown.\n\nNOT NEEDED ON A MODEL ALREADY TREATED: when read_ifc_overview returns\n'designation_existante', the units and fans are already designated -\nreuse them. Posting rules REPLACES that designation entirely: do it\nonly when the user asks to start again, or when the designation\nplainly contradicts what they say.\n\nTHIS IS HOW THE TOOL LEARNS A MODEL. read_ifc_overview gives you one\nline per family of types, not one per piece. You answer with\nRULES on those groups, and this tool applies them to the three thousand\npieces. You never give a verdict piece by piece: the result stays\ndeterministic because a program, not you, does the matching.\n\nTHEN READ THE ANSWER BACK, AND EXPECT TO POST AGAIN. The answer gives\nevery group with the role your rules gave it and how many pieces that\nis. A rule that is too wide shows up on one line — « Gaine\nrectangulaire cadree, 471 pieces, centrale_de_traitement_d_air » is a\nrule that turned every duct into an air handling unit. Narrow it and\npost again. Calling this tool costs nothing and may be repeated as\noften as you need.\n\nWHAT NEEDS A ROLE, AND WHAT DOES NOT. Plain ducts and fittings need\nnone: they are network by nature, and the answer marks them\nsegment_ou_raccord so you can see at a glance whether a rule caught\nthem by mistake. What needs a role is everything else — air handling\nunits, fans, fire dampers, balancing dampers, silencers, louvres,\ndiffusers — plus whatever must be kept OUT of the network, such as\naccess zones, equipment plinths or damper motors.\n\nTHREE ROLE NAMES ARE FIXED, because circuits start from them: give\nair handling units, monoblocs and ventilation casings the role\ncentrale_de_traitement_d_air, fans - and DUCTED fan coil units\n(ventilo-convecteurs gainables), which feed their own duct\nnetwork - the role ventilateur, and SMOKE\nEXHAUST fans - including fans that bring compensation air for smoke\nexhaust - the role ventilateur_desenfumage - exactly these words. A\nsmoke fan runs only in a fire, with the ventilation stopped: a duct\nit shares with an air handling unit is not a plenum shared by two\ninstallations, and the tool does not cut the networks there. Read\nthe names, families and types: « désenfumage », « DES », « smoke »,\n« Entrauchung », « RWA ». ONLY EQUIPMENT THAT MOVES THE AIR gets one of them: a\nunit is a box with a fan in it. Heating and cooling coils, heat\nexchangers, filters, silencers, dampers, fire dampers, VAV boxes,\nhumidifiers are NOT units: the air runs through them, they are\npieces of the network. Give them another role (coil, silencer,\ndamper...) or none - never one of the unit roles. A coil in\n'equipements' is a rule that is too wide. BUT A FAMILY WHOSE NAME\nSAYS IT IS A UNIT IS A UNIT - CTA, AHU, UTA, monobloc, caisson,\ncentrale, Lüftungsgerät - even when its type describes its heat\nrecovery: « BG_CTA_Echangeur à plaques » is an air handling unit\nwith plate heat recovery, not a heat exchanger. A heat exchanger is\na network piece only when it is a separate piece in a duct run. The answer lists, under\n'equipements', the GUIDs of every piece of the model that got one of\nthese roles: that list is what trace_duct_circuits starts from,\nand what the pages show as units.\n\nNETWORK COMPONENTS HAVE FIXED ROLE NAMES TOO, because the pressure\ndrop calculation gives each of them its loss: clapet_coupe_feu (fire\ndamper), clapet_desenfumage (smoke damper), clapet_anti_retour\n(non-return damper), registre (control, balancing or motorised\ndamper), regulateur_de_debit (constant airflow regulator, CAV),\nboite_vav (VAV box), silencieux (silencer), filtre (a filter fitted\nalone in a duct run), bouche (supply or return grille, diffuser,\nvalve), grille_exterieure (outdoor or weather louvre) - exactly these\nwords. A filter casing of an air handling unit is\ncomposant_de_monobloc, never filtre: it is part of the unit and\nnever counted in a circuit. Every other role name is yours to\nchoose.\n\nA MONOBLOC BUILT FROM MODULES. Many air handling units are modelled\nas casings set end to end, each its own piece: filter casing, coil\ncasing, heat exchanger or heat recovery casing, humidifier, washer,\nfan section, damper casing, empty casing. Give every such MODULE the\nrole composant_de_monobloc - exactly these words - and its fan\nsection(s) the unit role as usual. The tool then joins the modules\nthat touch each other face to face (over 0.25 m2 of contact) into ONE\nunit: every duct on any module becomes one of its branches, and two\nfans of the same casing become one unit. Only modules of a unit get\nthis role: a coil, a filter or a silencer fitted IN a duct is a piece\nof the network, and an equipment frame or plinth is not a module.\n\nORDER THE LIST YOURSELF, most specific first, down to the most\ngeneral.\nThe fire damper rule must come before the balancing damper rule, or\n« damper » takes everything. Equipment must come before terminals:\n« VEN_MSF_MONOBLOC_SIMPLE_FLUX_REPRISE » contains « reprise », and a\nreturn-diffuser rule placed first would claim the air handling unit.\n\nPieces no rule catches are simply listed, with no warning and no\nfailure: the engineer judges on the 3D view, not on a coverage report.\n\nNEXT: once 'equipements' lists the air handling units and fans you\nexpect, call trace_duct_circuits with only the token. It computes\nnothing yet: it checks that the units are connected to the networks\nand returns the complete list of units and fans, to choose from -\nsee trace_duct_circuits. 'equipements' counts every piece\n('pieces') but lists at most thirty names: the count, not the list,\nis the model.\n","inputSchema":{"type":"object","properties":{"token":{"description":"The model token, from ifc_upload_result or from the link the user pasted.","title":"Token","type":"string"},"rules":{"additionalProperties":true,"description":"Your rules, as a JSON object. The only required key is roles.liste: an ORDERED list, FIRST MATCH WINS, most specific first. Each entry is {\"role\": \"a_name\", \"si_un_de\": [conditions]} and may also carry si_tout_de (all must match) and sauf_si (none may match). A condition names one field or one property, and one operation:\n  {\"champ\": \"nom_du_type\", \"contient\": [\"cta\"]}\n  {\"propriete\": \"Mechanical.System Name\", \"commence_par\": [\"VEN_\"]}\nFields: classe, predefined_type, object_type, nom_brut, classe_du_type, nom_du_type, predefined_type_du_type, element_type_du_type - the same ones read_ifc_overview shows under 'identite'. Operations, from widest to narrowest: contient (anywhere, even inside a word), mot_commence_par (at the start of a word), commence_par (start of the string), finit_par (end of the string), mot_entier (a whole word), egal (the whole string). Case and accents are ignored, and _ - . / are read as spaces. You may also pass dimensions, noms_de_systeme and debits_et_pertes; they are kept as given.","title":"Rules","type":"object"}},"required":["token","rules"],"title":"apply_ifc_rulesArguments"},"annotations":{"title":"Apply your classification rules to the whole IFC model","readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"c01883547b352ff03384063500c8684166f05f312a002ed15d8e274784541b36","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"check_en378_zones","title":null,"description":"DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable.\n\nEN 378 applied to BUILDING projects, volume by volume.\n\nAn installation does not occupy one room but several: the machine, the rooms\ncrossed by refrigerant lines, the rooms served by indoor units. Each volume\nis classified on its own — access category (a/b/c) and location class (I–IV)\n— and each classification calls for its own measures. The tool answers per\nvolume, never as a single verdict.\n\nIt returns, for every volume: its classification and why, the charge limit\nfrom Tables C.1 and C.2 of EN 378-1 (with the C.2 formula computed when the\ntable calls for it), whether the charge exceeds it, the EN 378-3 measures\nthat follow, the applicable texts (EN 378-1 to -4, EN IEC 60079-10-1, SUVA\n66139 and 2153) and the ventilation flow rates.\n\nFOUR CONFIGURATIONS COVER ALMOST EVERY BUILDING PROJECT. Bring the user's\ncase back to one of them wherever possible:\n  machine_en_local_technique   chiller or heat pump, all refrigerant inside\n                               the machine, standing in a plant room -> c III\n  enceinte_accessible_fermee   all refrigerant inside a walk-in ventilated\n                               enclosure that stays closed even for\n                               maintenance -> the enclosure is c III, the\n                               room around it carries no requirement\n  enceintes_inaccessibles      one or more units, each in a manufacturer's\n                               non-accessible ventilated enclosure -> TWO\n                               analyses: the enclosure in operation (class\n                               IV, the manufacturer sizes and justifies it,\n                               ask him for the enclosure ventilation), and\n                               the plant room with the enclosure OPEN for\n                               maintenance, which comes back to c III\n  split_traversant             split or VRF outdoors, refrigerant lines\n                               crossing occupied rooms -> each room on its\n                               own; offices and their circulations are b I,\n                               and formula C.2 gives the maximum charge for\n                               the floor area, or the minimum floor area for\n                               the charge\n\nTHIS TOOL ANSWERS SAFETY IN THE ROOM. It says NOTHING about whether the\nrefrigerant may still be placed on the market or refilled: in Switzerland that\nis `check_refrigerant_switzerland`. A question that mixes both - « may I use\nR-32 for 3 kg in a server room, and until when can I refill it » - needs BOTH\ntools: call this one for the room, and check_refrigerant_switzerland for the\ndates. Do not answer half the question.\n\nNEVER guess. The refrigerant, the configuration and the charge are always\nneeded; a split also needs the floor area and how the indoor unit is mounted\n(floor, wall, window, ceiling), since C.2 depends on it. Without them the\nresult is `provisional` and carries `questions_to_ask`: ask them, one or two\nat a time, then call again.\n\nAnswer from `answer_outline`, volume by volume. In building projects,\ndetection is preferred over treating a plant room as an ATEX zone. C.3 is\nnever used. Say that the practical limit alone proves nothing: the charge\nlimit of Tables C.1 and C.2 is what counts.\n\nSCOPE: building services. Cold rooms, food refrigeration and industrial\nprocess refrigeration are a different trade.\n","inputSchema":{"type":"object","properties":{"refrigerant":{"description":"Refrigerant as the user wrote it: 'R-32', 'R410A', 'R290', 'R717', 'propane'…","title":"Refrigerant","type":"string"},"configuration":{"anyOf":[{"enum":["machine_en_local_technique","enceinte_accessible_fermee","enceintes_inaccessibles","split_traversant"],"type":"string"},{"type":"null"}],"default":null,"description":"How the installation is laid out. Omit if unknown: the tool returns the question to ask.","title":"Configuration"},"charge_kg":{"anyOf":[{"exclusiveMinimum":0,"maximum":100000,"type":"number"},{"type":"null"}],"default":null,"description":"Refrigerant charge of the largest circuit, in kg.","title":"Charge Kg"},"volume_local_m3":{"anyOf":[{"exclusiveMinimum":0,"maximum":10000000,"type":"number"},{"type":"null"}],"default":null,"description":"Volume of the plant room, in m³.","title":"Volume Local M3"},"volume_enceinte_m3":{"anyOf":[{"exclusiveMinimum":0,"maximum":10000000,"type":"number"},{"type":"null"}],"default":null,"description":"Volume of the ventilated enclosure, in m³.","title":"Volume Enceinte M3"},"volume_local_desservi_m3":{"anyOf":[{"exclusiveMinimum":0,"maximum":10000000,"type":"number"},{"type":"null"}],"default":null,"description":"Volume of the smallest room crossed or served by an indoor unit, in m³.","title":"Volume Local Desservi M3"},"surface_local_desservi_m2":{"anyOf":[{"exclusiveMinimum":0,"maximum":1000000,"type":"number"},{"type":"null"}],"default":null,"description":"Floor area of that room, in m². Formula C.2 needs it; without it the tool returns the minimum area required instead.","title":"Surface Local Desservi M2"},"pose":{"anyOf":[{"enum":["sol","mural","fenetre","plafond"],"type":"string"},{"type":"null"}],"default":null,"description":"How the indoor unit is mounted: on the floor, wall, window or ceiling. Formula C.2 depends on it.","title":"Pose"},"acces_local":{"anyOf":[{"enum":["a","b","c"],"type":"string"},{"type":"null"}],"default":null,"description":"Access category of the plant room. Omit: 'c', authorised persons only.","title":"Acces Local"},"acces_locaux_desservis":{"anyOf":[{"enum":["a","b","c"],"type":"string"},{"type":"null"}],"default":null,"description":"Access category of the rooms crossed or served: 'b' for offices, laboratories, workplaces; 'a' for hotels, schools, shops, hospitals, homes.","title":"Acces Locaux Desservis"},"language":{"default":"fr","description":"The user's language. Texts are in French: translate them.","enum":["fr","de","en","es","it"],"title":"Language","type":"string"}},"required":["refrigerant"],"title":"check_en378_zonesArguments"},"annotations":{"title":"EN 378 safety check, volume by volume (building projects) — deterministic","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"f8e774e5b023ed0fd0f0ff2ba3eb15040d472e2767480667066de10c9a8a54a5","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"check_refrigerant_switzerland","title":null,"description":"DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the regulation's annexes and thresholds, never from a language model's estimate. Every step is auditable.\n\nSwiss refrigerant regulation check (ORRChim / ChemRRV annex 2.10, OFEV synthesis\nof May 2026, rules adopted 29.10.2025) plus refrigerant data from EN 378-1\nAnnex E: GWP (AR4, the ORRChim basis), ODP, LFL, safety class, practical limit.\n\nReturns, for a given refrigerant and installation: the date from which machines\nusing it can no longer be placed on the Swiss market (import from 01.01.2027,\nsale to third parties from 01.07.2027), the date from which filling with virgin\nrefrigerant is banned, the period when only reclaimed refrigerant may be used,\nand the date from which all filling is banned.\n\nSCOPE: heating, air conditioning, building cooling and process cooling,\ndata centres included. NOT food refrigeration, cold rooms or deep freezing:\nthose are a different trade, and the tool declines them instead of\nanswering.\n\nUse it whenever the user asks about a refrigerant in Switzerland — its GWP / PRG,\nflammability, whether a chiller, heat pump, split, VRF or cold room using it may\nstill be sold or refilled — in any language: fluide frigorigène, Kältemittel,\nrefrigerante, refrigerant, R-32, R-410A, R-290, CO2, NH3...\n\nThe answer depends on the installation. The regulation distinguishes:\nuse (building cooling, food refrigeration medium / low temperature / combined /\ndeep freezing, process cooling, heat pump mainly for heating, ice rink), cooling\ncapacity Q0K or heating capacity Q0H, self-contained (factory-built packaged\nunit) or not, split, direct expansion (incl. VRF), secondary coolant loop\n(chilled water / brine), air-cooled condenser and refrigerant charge.\nTHIS TOOL ANSWERS ONE QUESTION ONLY: may the refrigerant still be sold and\nrefilled in Switzerland, and until when. It says NOTHING about safety in the\nroom - charge limits, machine room, detection, ventilation, ATEX. That is\n`check_en378_zones`. A question that mixes both - « may I use R-32 for 3 kg in\na server room, and until when can I refill it » - needs BOTH tools: call this\none for the dates, and check_en378_zones for the room. Do not answer half the\nquestion.\n\nNEVER guess these. Call the tool with what the user gave: it returns\n`provisional: true`, the possible `scenarios`, and `questions_to_ask` in the\norder that matters most. Ask them (one or two at a time), then call again.\nNatural refrigerants need no questions. Build your answer on `answer_outline`;\nquote exceptions as possible, never as granted.\n","inputSchema":{"type":"object","properties":{"refrigerant":{"description":"Refrigerant designation as the user wrote it: 'R-32', 'R410A', 'R1234ze', 'CO2', 'propane'…","title":"Refrigerant","type":"string"},"application":{"anyOf":[{"enum":["climatisation_batiment","froid_alimentaire_positif","froid_alimentaire_negatif","froid_alimentaire_combine","surgelation","froid_process","pac_chauffage","patinoire_permanente","patinoire_temporaire"],"type":"string"},{"type":"null"}],"default":null,"description":"Use of the installation: 'climatisation_batiment' (building cooling, incl. reversible heat pump used mainly for cooling), 'froid_alimentaire_positif' (food/perishables, use temp ≥ 0 °C), 'froid_alimentaire_negatif' (≥ −25 °C), 'froid_alimentaire_combine' (multiplex medium + low temp with common discharge), 'surgelation' (< −25 °C), 'froid_process' (industrial process cooling), 'pac_chauffage' (heat pump mainly for heating), 'patinoire_permanente', 'patinoire_temporaire'. Omit if unknown.","title":"Application"},"cooling_capacity_kw":{"anyOf":[{"exclusiveMinimum":0,"maximum":100000,"type":"number"},{"type":"null"}],"default":null,"description":"Peak useful cooling capacity Q0K, kW. Omit if unknown.","title":"Cooling Capacity Kw"},"heating_capacity_kw":{"anyOf":[{"exclusiveMinimum":0,"maximum":100000,"type":"number"},{"type":"null"}],"default":null,"description":"Peak useful heating capacity Q0H, kW (heat pumps). Omit if unknown.","title":"Heating Capacity Kw"},"refrigerant_charge_kg":{"anyOf":[{"exclusiveMinimum":0,"maximum":100000,"type":"number"},{"type":"null"}],"default":null,"description":"Total refrigerant charge, kg. Omit if unknown.","title":"Refrigerant Charge Kg"},"self_contained":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True if 'autonome': factory-built circuits in a frame/casing and no gas-carrying part connected on site (packaged chiller, monobloc heat pump, rooftop). Omit if unknown.","title":"Self Contained"},"split":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True for a split system (indoor/outdoor units linked by refrigerant lines laid on site). Omit if unknown.","title":"Split"},"direct_expansion":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True if the refrigerant evaporates directly in the room units / evaporators (DX, incl. VRF); False if it cools a water or brine loop. Omit if unknown.","title":"Direct Expansion"},"secondary_circuit":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True if cold is distributed through a secondary coolant loop (chilled water, glycol, brine). Omit if unknown.","title":"Secondary Circuit"},"air_cooled_condenser":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True if heat is rejected through an air-cooled condenser (heat pump: its air heat exchanger). Omit if unknown.","title":"Air Cooled Condenser"},"evaporator_count":{"anyOf":[{"maximum":1000,"minimum":1,"type":"integer"},{"type":"null"}],"default":null,"description":"Number of evaporators.","title":"Evaporator Count"},"refrigerant_circuit_count":{"anyOf":[{"maximum":100,"minimum":1,"type":"integer"},{"type":"null"}],"default":null,"description":"Number of refrigerant circuits.","title":"Refrigerant Circuit Count"},"heat_recovery":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True if rejected heat is recovered.","title":"Heat Recovery"},"simultaneous_heating_cooling":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True for simultaneous heating and cooling with at least 2 air heat exchangers.","title":"Simultaneous Heating Cooling"},"gwp_if_unlisted":{"anyOf":[{"maximum":30000,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"ONLY if a previous call said the refrigerant is not in the database: its GWP (AR4) from the manufacturer's datasheet, given by the user.","title":"Gwp If Unlisted"},"odp_if_unlisted":{"anyOf":[{"maximum":20,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"ONLY with gwp_if_unlisted: its ODP (0 for HFC/HFO).","title":"Odp If Unlisted"},"family_if_unlisted":{"anyOf":[{"enum":["naturel","stable","hfo"],"type":"string"},{"type":"null"}],"default":null,"description":"ONLY with gwp_if_unlisted: 'naturel' (natural), 'stable' (contains any HFC/PFC — e.g. R-454B, R-454C, R-455A), 'hfo' (only HFO and/or natural components).","title":"Family If Unlisted"},"language":{"default":"en","description":"The user's language, for labels. French or English text; translate for de/it/es.","enum":["fr","de","en","es","it"],"title":"Language","type":"string"}},"required":["refrigerant"],"title":"check_refrigerant_switzerlandArguments"},"annotations":{"title":"Swiss refrigerant regulation check (ORRChim annex 2.10) — deterministic","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"059c187f5cc82f7a60c4ee89d3cd8d6445367165f7db7e367dd76445fcf6ec0a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"ifc_upload_result","title":null,"description":"Where the upload stands. When `state` is `depose`, `token` is the\ntoken to pass to read_ifc_networks.","inputSchema":{"type":"object","properties":{"upload_token":{"description":"The upload_token returned by open_ifc_upload.","title":"Upload Token","type":"string"}},"required":["upload_token"],"title":"ifc_upload_resultArguments"},"annotations":{"title":"State of an IFC upload started with open_ifc_upload","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"e8c56cbd830c8905f396186272d3d2c2f42d189844fb0c1bb194140e72c07793","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"name_ifc_networks","title":null,"description":"Apply the names you propose, and get back the updated report.\n\nTHE NAMES ARE YOURS, THE NETWORKS ARE NOT. You are naming what the\ntool measured; you are not changing what it measured. Nothing you\nsend here alters a network, a part, or a correction.\n\nWHAT COMES BACK. The updated report, a 3D link where the user sees\nyour names in colour, and a link to the corrective Dynamo script that\nwrites the systems back into Revit.\n\nALWAYS GIVE THE USER THE 3D LINK, and say plainly which names are\nyours. Networks are deterministic; names are a proposal. A user who\ncannot tell the two apart cannot check your work.\n\nAFTER THE USER HAS BEEN IN THE 3D VIEW, call read_ifc_networks again\nwith the same token before saying anything about the model. They may\nhave renamed what you proposed, assigned parts by hand, or refused a\ncorrection — and only a fresh read shows it.\n","inputSchema":{"type":"object","properties":{"token":{"description":"The same token used with read_ifc_networks.","title":"Token","type":"string"},"names":{"additionalProperties":true,"description":"One name per network, keyed by its 'rang' as a string, for instance: {'3': 'SUPPLY L2', '7': 'EXTRACT KITCHEN'}. Only include the ones you are naming; the others are left untouched.","title":"Names","type":"object"},"reasoning":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"One short line per name, saying what it is based on — the neighbouring unit, the project's naming scheme, an existing system. Shown to the user, who decides.","title":"Reasoning"}},"required":["token","names"],"title":"name_ifc_networksArguments"},"annotations":{"title":"Name the networks of an IFC model","readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"4e52cc421ddbe5bad25f53f46f6acf507d9f902ddac74f68e8419b71520904c2","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"open_ifc_upload","title":null,"description":"Show an upload box in the conversation where the user can drop an\nIFC file (.ifc) of a building services model (HVAC, plumbing,\nheating). The file goes straight from the user's browser to\nthenewengineer.com - you never see it.\n\nCALL THIS when the user wants to analyse an IFC model and has not yet\ngiven you a link from thenewengineer.com. Then tell the user to drop\nthe file in the box.\n\nWhen the upload is done, the box posts a message with a token. Use\nthat token with read_ifc_networks. If no message arrives and the user\nsays the upload is done, call ifc_upload_result with the upload_token\nreturned here.\n\nPrototype: files up to the anonymous size limit of the site.","inputSchema":{"type":"object","properties":{},"title":"open_ifc_uploadArguments"},"annotations":{"title":"Open an upload box for an IFC model, inside the conversation","readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"7d4d92b74e265b3f0e8595016a8075b8adc06740c243d42546aea62aeea785d4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"read_ifc_networks","title":null,"description":"DETERMINISTIC: networks come from geometry, not from a guess. The\nsame model always gives the same networks, from any AI, on any day.\n\nRead the networks of an IFC model already uploaded by the user.\n\nWHAT A NETWORK IS. A set of parts that touch each other, cut at\nequipment: a pump, an air handling unit, a chiller separates two\nsystems, so the tool does not run through them. This is measured on\nthe geometry — you cannot and need not check it.\n\nWHAT YOU GET, PER NETWORK\n  state          'homogeneous' — a system exists, some parts were\n                 mis-named by the modeller; the tool will correct them.\n                 'undetermined' — no system can be read. THIS is where\n                 you are useful.\n                 'assigned' — the user or you already named it.\n  system         the dominant name, when there is one\n  part_dominante the share of named parts carrying it\n  equipements_voisins  the NAMES of the machines this network is\n                 connected to. An undetermined network starting from\n                 'AHU-Supply-L2' names itself — but only you can see it.\n  systemes_existants   every system name already in the model\n\nWHAT TO DO NEXT. Propose a name for each undetermined network, using\nthe neighbouring equipment, the existing system names, and anything\nthe user told you about the project's naming scheme. Ask the user for\ntheir list of planned systems if you do not have it. Then call\nname_ifc_networks.\n\nWHAT NOT TO DO. Do not rename a network the report calls\n'homogeneous' unless its name plainly contradicts the equipment it is\nconnected to — and then say why. Do not invent a network: you cannot\nsee the geometry, and the tool already did that work.\n\nCALL THIS AGAIN WHENEVER THE STATE MAY HAVE MOVED. The token stays\nvalid for 48 hours and is a key, not a snapshot: every call recomputes\nand returns the model AS IT IS NOW. The user works in the browser\nbetween your messages — renaming networks, assigning parts by hand,\naccepting or refusing corrections. So the moment they say they have\ndone something, or you are about to state a figure, call this tool\nagain.\n\nNEVER ANSWER FROM MEMORY about networks, counts or states. What you\nread earlier is already out of date the moment the user touches the\n3D view, and a stale figure stated confidently is worse than no\nfigure at all.\n","inputSchema":{"type":"object","properties":{"token":{"description":"The token from the link the user pasted. It looks like the last part of thenewengineer.com/ia/XXXX. The user gets it on the model page, button 'share with my AI'. Valid 48 hours, one model.","title":"Token","type":"string"}},"required":["token"],"title":"read_ifc_networksArguments"},"annotations":{"title":"Networks and systems of an IFC model — deterministic","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"0a371217281796c68dbea2eb1c6145bab6abedccc83c7c7330b3bcba3f401ca7","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"read_ifc_overview","title":null,"description":"CALL THIS FIRST, as soon as the user gives you a token - a link\nthenewengineer.com/ia/XXXX pasted in the conversation - BEFORE you\nanswer anything, even when the user only says they will choose or do\nsomething themselves. It answers within seconds, while the network\ngraph is still being built - use that time to think.\n\nTHE USER WANTS TO CHOOSE THE UNITS THEMSELVES (« let me select »,\n« je vais choisir les centrales »): the place to do it is the\ncontrol page. Go on through the steps below until trace_duct_circuits (token\nonly) returns 'lien_centrales', and GIVE THEM THAT LINK. Never tell\nthem to select « in the interface » without the link: there is no\nother place to select.\n\nA MODEL ALREADY TREATED: if the answer carries\n'designation_existante', an earlier session already designated the\nunits and fans of this model. Reuse it: skip step 2, go straight to\ntrace_duct_circuits, and show the user the designation you reused.\nPost new rules only if the user asks to start again.\n\nTHE CIRCUITS OF A MODEL IN FOUR CALLS:\n  1. read_ifc_overview - this call: the types of the model.\n  2. apply_ifc_rules - your rules. Give air handling units,\n     monoblocs and ventilation casings the role\n     centrale_de_traitement_d_air, fans the role ventilateur, and\n     smoke exhaust fans (and smoke compensation fans) the role\n     ventilateur_desenfumage, exactly these words - and ONLY to\n     equipment that holds a fan.\n     Coils, heat exchangers, filters, silencers, dampers, VAV boxes\n     are pieces of the network, not units - BUT a family NAMED as a\n     unit (CTA, AHU, UTA, monobloc, caisson, centrale) is one, even\n     when its type names its heat recovery: « BG_CTA_Echangeur à\n     plaques » is an air handling unit. Its answer lists under\n     'equipements' every unit and fan of the model.\n  3. trace_duct_circuits with ONLY the token - it computes nothing,\n     walks the networks from every unit and fan, and either returns\n     the COMPLETE list of units and fans with the control page, or\n     says the units could not be connected to the model's networks.\n  4. trace_duct_circuits again with the units the user wants, or\n     all_networks=true for all of them (offered up to 50 air\n     networks only).\nThe answer of this call repeats these steps under 'marche_a_suivre'.\n\nYOU SEE A SAMPLE, THE TOOL SEES EVERYTHING. This overview shows one\nexample per type, not every piece: you cannot count the units, the\nfans or the networks of the model from it, and you must not believe\nyou have seen them all. The tool applies your rules to every piece\nand walks every network. So never pick the networks to compute from\nthis overview: trace_duct_circuits gives you the complete list of\nunits and fans first, and you choose from THAT list.\n\nWHAT YOU GET. Not 3 000 parts: an INDEX of the model, one line per\nFAMILY of types (the sizes of one family share its line) - dampers,\nterminals, equipment, proxies -, each with its IFC class, its number\nof pieces, an example GUID and the identity fields of its largest\ntype ('identite': object_type, nom_du_type...), which is what rules\nare written on. Plain ducts and fittings need no role: they are\nlisted in one line each under 'reseau_ordinaire', and\n'cotes_exemples' shows the numeric properties of the main duct\nfamilies - where height, width and diameter are.\n\nTHE DETAIL, ON DEMAND. When a family's name does not tell you what\nit is, call this tool again with families=[its 'famille' names] (up\nto 12 per call): you get every property of an example piece and\nevery type of the family. property_catalogue=true lists every\nproperty of the model once. These follow-up calls bill nothing.\n\nWHAT TO DO WITH IT. Write RULES, not verdicts. For roles: which words,\nin which field, identify a fire damper, a silencer, a balancing\ndamper, an air terminal, an air handling unit, a fan, a pump - and\nwhich groups are NOT network at all (access zones, plinths,\nplaceholders, damper motors). For sizes: which 'PropertySet.Property'\nholds height, width, diameter, length. A rule applies to every part,\nincluding those you were not shown, and to the user's next models.\n\nTRAPS the field 'a_savoir' warns about: values are in the FILE's unit\n(see metres_par_unite), not millimetres; insulation sizes and\nhydraulic diameters look like dimensions and are not.\n\nThe field 'etat_du_graphe' says whether the networks are ready yet:\n'pret' means read_ifc_networks will answer now.","inputSchema":{"type":"object","properties":{"token":{"description":"The token from the link the user pasted — the last part of thenewengineer.com/ia/XXXX. Valid 48 hours.","title":"Token","type":"string"},"families":{"anyOf":[{"items":{"type":"string"},"type":"array"},{"type":"null"}],"default":null,"description":"Leave EMPTY on the first call. Then, to read EVERY property of some families, their 'famille' names from the first answer - at most 12 per call. Only the detail asked for comes back.","title":"Families"},"property_catalogue":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True lists every property of the model once, by property set, with an example value - to find which 'PropertySet.Property' holds a size or a flow. Only the catalogue comes back.","title":"Property Catalogue"}},"required":["token"],"title":"read_ifc_overviewArguments"},"annotations":{"title":"Types and properties of an IFC model — what rules to write","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"d27ec91eb40e98983e69db92406993b3ba42b432666cb09fb6565ce193c7e8e3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"size_expansion_vessel","title":null,"description":"DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable.\n\nSize the expansion vessel and pressurisation of a closed heating or\n    chilled-water circuit to EN 12828: static height, minimum pressure p0,\n    fill pressure pa, final pressure pe, expansion volume, water reserve,\n    nominal vessel volume with the standard vessel to buy, safety valve\n    setting together with the minimum it must not fall below, pressure\n    class of the lowest equipment, intermediate vessel when needed.\n\n    Heights become pressures through the real density of the fluid, at the\n    temperature that matters for each: the coldest for p0, the design\n    temperature for the valve and the lowest point. Water and glycols\n    therefore give different figures for the same height.\n\n    Use it whenever the user asks to size or check an expansion vessel,\n    pressurisation unit, pre-charge pressure or safety valve — in any\n    language: vase d'expansion, maintien de pression, Ausdehnungsgefäss,\n    Druckhaltung, vaso di espansione, vaso de expansión.\n\n    Needs the installation water volume and THREE heights, all measured\n    from the point where the expansion vessel connects to the network:\n      - the highest point of the installation, above it;\n      - the lowest point, usually below it (negative) or level with it;\n      - the safety valve, which always sits on the heat generator or\n        chiller. If the user does not know it, it is assumed 1 m above\n        the vessel connection, and the result says so.\n    Ask the user for the volume and the three heights before calling.\n    NEVER invent a height: if the lowest point or the valve height is\n    unknown, omit it. The result is then marked provisional and lists\n    the questions to ask. Build your answer on `answer_outline`: it\n    carries the assumptions, the questions and the link to the website,\n    which measures all of these on the user's IFC model.\n    ","inputSchema":{"type":"object","properties":{"installation_volume_l":{"description":"Total water content of the closed circuit, in litres: pipes, emitters, generator, buffer tank. THIS IS THE WATER, NOT THE VESSEL. If you know the vessel and want the water content, this is the wrong tool: call water_content_from_vessel.","exclusiveMinimum":0,"maximum":5000000,"title":"Installation Volume L","type":"number"},"highest_point_above_unit_m":{"anyOf":[{"maximum":300,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"Height 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. NEEDED FOR A STATIC VESSEL ONLY: a compressor or pump unit holds the pressure itself, and heights play no part in its sizing — do not ask for them.","title":"Highest Point Above Unit M"},"lowest_point_from_unit_m":{"anyOf":[{"maximum":300,"minimum":-300,"type":"number"},{"type":"null"}],"default":null,"description":"Height 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.","title":"Lowest Point From Unit M"},"safety_valve_from_unit_m":{"anyOf":[{"maximum":300,"minimum":-300,"type":"number"},{"type":"null"}],"default":null,"description":"Height 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.","title":"Safety Valve From Unit M"},"installation":{"anyOf":[{"enum":["chauffage","refroidissement"],"type":"string"},{"type":"null"}],"default":null,"description":"'chauffage' for heating, 'refroidissement' for cooling / chilled water. Omit: heating.","title":"Installation"},"fluid":{"anyOf":[{"enum":["eau","meg","mpg","tyfocor"],"type":"string"},{"type":"null"}],"default":null,"description":"Heat-transfer fluid: 'eau' (Water), 'meg' (MEG), 'mpg' (MPG), 'tyfocor' (TYFOCOR L (MPG)). Omit: plain water.","title":"Fluid"},"glycol_pct":{"anyOf":[{"maximum":60,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Glycol concentration in %, ignored for water. Defaults to 30 %.","title":"Glycol Pct"},"flow_temperature_c":{"anyOf":[{"maximum":100,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Flow temperature, °C. Omit: 80 in heating, 6 in cooling.","title":"Flow Temperature C"},"return_temperature_c":{"anyOf":[{"maximum":100,"minimum":-20,"type":"number"},{"type":"null"}],"default":null,"description":"Return temperature, °C. Omit: 60 in heating, 12 in cooling.","title":"Return Temperature C"},"filling_temperature_c":{"anyOf":[{"maximum":90,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Temperature at which the circuit is filled, °C. Omit: 10.","title":"Filling Temperature C"},"min_temperature_c":{"anyOf":[{"maximum":100,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"LOWEST temperature the fluid can reach, °C — including a breakdown, not just normal running. Omit and the filling temperature is used; in a glycol mix the calculation already goes down to the frost protection point.","title":"Min Temperature C"},"design_temperature_c":{"anyOf":[{"maximum":100,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Hottest the fluid ever gets, standstill included. Omit: the warmer of flow and return in heating, 40 °C in cooling.","title":"Design Temperature C"},"pressurisation":{"anyOf":[{"enum":["statique","compresseur","pompe"],"type":"string"},{"type":"null"}],"default":null,"description":"Type of pressurisation: 'statique' (Pressure-maintained by gas cushion (Statico)), 'compresseur' (Compressor-driven (Compresso)), 'pompe' (Pump-driven (Transfero)). Omit: gas-cushion vessel.","title":"Pressurisation"},"safety_valve_setting_bar":{"anyOf":[{"maximum":10,"minimum":2,"type":"number"},{"type":"null"}],"default":null,"description":"Safety 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.","title":"Safety Valve Setting Bar"},"minimum_required_pressure_bar":{"anyOf":[{"maximum":10,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Pressure 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.","title":"Minimum Required Pressure Bar"},"language":{"default":"en","description":"The user's language, for labels and alerts.","enum":["fr","de","en","es","it"],"title":"Language","type":"string"}},"required":["installation_volume_l"],"title":"size_expansion_vesselArguments"},"annotations":{"title":"Expansion vessel SIZE from the water content (EN 12828) — deterministic","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"c63d1cd4889c4ef3611bde2308d51c80abf9ffbdf23bc207711c33ab40247562","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"trace_duct_circuits","title":null,"description":"THE CIRCUITS THE FANS OF A MODEL ARE SIZED ON, found without anyone\nclicking and computed on the pressure-drop page, where the user\nconfirms types and flows and reads the pressure drops.\n\nTHE USER WANTS TO PICK THE UNITS THEMSELVES: call this tool with ONLY\nthe token right away, and give them 'lien_centrales' - the control\npage, where a click turns a unit red and 'Send to my AI' sends you\ntheir choice.\nWithout that link they have nowhere to select.\n\nONLY UNITS AND FANS ARE EXCHANGED. The tool never sends you system\nnames: it sends the air handling units and fans your rules found,\neach with what the network walk finds connected to it - geometry,\nnot names. A unit is equipment with a FAN - air handling unit,\nmonobloc, ventilation casing, fan. Coils, heat exchangers, filters,\nsilencers, dampers are network pieces: if one shows up in the list\n(often as 'dans_le_reseau_de' another unit), your rules are too\nwide - fix them with apply_ifc_rules before choosing. But a family\nNAMED as a unit (CTA, AHU, monobloc) is one, whatever its type says.\nA LOW 'raccordement' MOSTLY MEANS MISSED UNITS: look for families\nnamed CTA, AHU, monobloc, caisson that got no unit role, and add\nthem before sending the user anywhere.\n\nFIRST THE CHECK AND THE LIST, THEN THE CALCULATION. Called with only\nthe token, once your rules are posted with apply_ifc_rules, it\ncomputes NOTHING and bills nothing. It walks the networks from every\nunit and fan and measures the share of the model's air pieces they\nreach ('raccordement'). Two answers:\n  - CONNECTED (half of the air pieces or more): the COMPLETE list of\n    units and fans ('centrales_et_ventilateurs', each with its\n    number of connected networks) and 'lien_centrales', the\n    CONTROL PAGE ('Network check' in English, 'Contrôle des\n    réseaux' in French) - not a view-only page: every unit in its colour\n    with its networks, where the user checks and CORRECTS the\n    connections (identify or remove a unit, add a virtual AHU,\n    connect or separate two parts, cross a shared plenum) before\n    anything is computed. Ask them to check it FIRST and wait for\n    their answer. There they can also open the calculation page\n    directly, or CLICK the units to compute: they turn red, and 'Send\n    to my AI' copies a new link carrying that choice. Give the\n    user that link, say nothing is computed yet, and that they can\n    tick there or name the units here. Then:\n      * the answer carries 'choix_de_l_utilisateur' (the user\n        ticked on the page): compute EXACTLY those names with\n        units, as its 'consigne' says - do not ask them again;\n      * the user named units, even loosely: map their words onto\n        the EXACT names of the list, say which you picked, and call\n        again with units;\n      * the user asked for the whole model and the list says\n        'tous_possible' (50 air networks or fewer): call again with\n        all_networks=true;\n      * otherwise show the user the WHOLE list to tick - every unit\n        and fan, however long; never only the main ones. 'Tous'\n        first when it is offered, then one numbered line per unit\n        with its number of connected networks; mark the units\n        connected to nothing. Filter only on what the user said,\n        and then say which filter and how many lines it left out.\n        Call with what they tick.\n  - NOT CONNECTED ('non_raccorde': less than half, or no unit at\n    all): tell the user the sentence of 'A_DIRE_A_L_UTILISATEUR' -\n    « Nous n'avons pas pu connecter les centrales de traitement\n    d'air aux réseaux de votre modèle », in their language - and\n    suggest the pressure-drop page ('lien_pdc'), where they define\n    each network themselves by a start and an end. Nothing is\n    computed. If your rules missed units, fix them and call again.\nWHAT IS COMPUTED: for each network connected to a chosen unit or\nfan, the LONGEST path. Networks connected to no unit are not\ncomputed here.\nBEYOND 50 AIR NETWORKS, THE MODEL IS COMPUTED ONE UNIT AT A TIME.\nEach call computes ONE unit - unit_name, or units with a single\nname - or the network of ONE piece - network_guid. The whole model,\nstart_role and several units are refused: nothing is computed, and\nthe answer says why. Ask the user which unit, or which piece: on the\ncontrol page, hovering a piece shows its GUID, and a click ticks a unit.\nUnits the user ticked on the page ('choix_de_l_utilisateur') are\nasked for: compute them one per call, one after the other. Never pick the units\nyourself, never go through them all in a row on your own, and never\ncall in parallel (sub-agents, simultaneous calls): the calls on one\nmodel run one after the other on the server, and parallel calls only\nslow the site down for everyone. Call again for the next one the user\nasks for; what is computed stays, and is not billed again.\n\nYOU SEE A SAMPLE IN THE OVERVIEW, THE WHOLE MODEL HERE. Never choose\nthe units from what read_ifc_overview showed you - one example per\ntype: choose from the list this tool returns.\n\nA REQUEST THE TOOL CANNOT MATCH. Names that match nothing come back\nunder 'non_reconnus', each with the closest names; the names that\ndid match are computed. If NOTHING matched - or the GUID or\nunit_name is unknown - nothing is computed, whatever the size of\nthe model: the list comes back, with the closest names under\n'non_reconnus' and what went wrong under 'demande_non_satisfaite'.\nCorrect the names from the list, or ask the user which one they\nmeant, and call again.\n\nA PIECE INSTEAD OF A UNIT. When the model has no unit, when the\nunit the user means was not recognised, or when they simply show a\npiece: network_guid computes the network of any piece - the tool\nfinds where its air starts; end_guid computes one circuit to that\nend - from start_guid if given, else from the start the tool finds.\nA start found by the tool comes back under 'depart_trouve' with what\nmade it chosen: say so, and ask the user to check it on the 3D link.\nThe user gets a GUID by hovering a piece on the control page.\nThese work on complex models too: they designate one network.\n\nONE UNIT BY ITS NAME. unit_name computes the unit or\nfan of that name, found among all the pieces - units does the same\nfor several. start_guid starts from\none part - an air handling unit, a fan, a duct - and computes the\nnetwork it belongs to, nothing else. The answer says so under 'portee' and\nlists the model's other units and fans under 'autres_departs': tell\nthe user the result is partial.\n\nFrom each starting part it keeps ONE CIRCUIT PER BRANCH: the longest\npath in metres of each branch. From an air handling unit, that is one\ncircuit per network connected to it - supply, return, intake,\nexhaust.\n\nEACH OF THESE CIRCUITS IS COMPUTED, and becomes a circuit of the\nmodel: it has a name, a COLOUR, and a tab on the website. All the\ncircuits of one unit or fan share THAT UNIT'S colour; on the page,\nits networks show in a light version of it, and networks connected\nto no unit in grey.\n\nWHAT YOU GET\n  portee          what the call covers: the whole model, one role,\n                  or one part's network only.\n  circuits        one per branch: name, colour, length, its unit,\n                  its current type, the flow used at the start and\n                  where it came from. NO PRESSURE DROP: see below.\n  autres_arrivees shorter paths, found but NOT computed.\n  lien_3d         the calculation page: every unit's networks in\n                  its colour, its circuits in a deeper shade.\n  lien_centrales  the control page: the units and their networks,\n                  where the user checks and corrects the\n                  connections and ticks the units to compute.\n                  ALWAYS give it, as a full URL, at the top of your\n                  answer - also after a calculation: it is the view\n                  the user needs most. Never describe it without\n                  its link.\n  lien_classeur   the Excel workbook of the computed circuits: the\n                  supply / return ","inputSchema":{"type":"object","properties":{"token":{"description":"The model token, from ifc_upload_result or from the link the user pasted.","title":"Token","type":"string"},"start_guid":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Leave EMPTY in general. The piece the AIR LEAVES FROM - an air handling unit, a fan, or the duct end where the air enters: circuits are computed from it. A GlobalId from 'equipements' in the answer of apply_ifc_rules, from read_ifc_networks, from read_ifc_overview (guid_exemple), or clicked by the user on the 3D link. For a piece somewhere IN the network, use network_guid instead: the tool finds the start. With end_guid: the one circuit between the two. Not together with start_role.","title":"Start Guid"},"end_guid":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"The END of ONE circuit the user wants - a terminal, a louvre, any duct. With start_guid: the circuit from start to end. Alone: the tool finds the start of that network, as for network_guid. Only this circuit is computed, on the path the network walk takes; it never replaces the circuits found by the tool.","title":"End Guid"},"network_guid":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"ANY piece of the network the user wants computed - a duct, a terminal, a fitting - when the model has no unit, when the user's unit was not recognised, or when they simply point at the network. The tool walks from it and finds where the air starts: a unit or fan of your rules touching that network (the closest), else a unit found by its IFC class, else the network's largest free duct end. It then computes THAT network only. The start found comes back under 'depart_trouve'. Alone - not with start_guid, end_guid, a name, units or a role.","title":"Network Guid"},"start_role":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Rarely needed. Computes every piece your rules gave this role - centrale_de_traitement_d_air or ventilateur -, like all_networks restricted to one role, and only on a model of 50 air networks or fewer whose units are connected. Prefer units. Not together with start_guid.","title":"Start Role"},"max_velocity_m_s":{"anyOf":[{"maximum":12,"minimum":0.5,"type":"number"},{"type":"null"}],"default":null,"description":"Design velocity, in m/s, 0.5 to 12. It sets the flow rate at the start of each circuit when flow_m3h is not given, and the flow after each branch: between two branches, the length-weighted average velocity of the straight ducts equals it, and no duct exceeds it by more than 20 %. Ventilation: 4 to 6 in main ducts, 2 to 3 near the terminals. ASK THE USER rather than guessing. Omit: the model default, 5 m/s.","title":"Max Velocity M S"},"flow_m3h":{"anyOf":[{"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Flow rate leaving ONE starting part, m3/h - so give it with start_guid. Over the whole model it would give every unit the same flow, and the call refuses it when there are several: compute the model without it, then call once per unit whose flow you know - its circuits are reused, only their flows change. Every circuit leaving that part carries it on its first stretch, and the flows further on are scaled from it - it sets the real velocity. BEFORE GUESSING, LOOK FOR IT: run read_ifc_overview and read the properties of the air handling unit, the fan or the casing you are starting from - a field named Debit, Flow, Air Flow, Luftmenge or Portata, often under a flow property set. Pass what you find, say where it came from, and convert it to m3/h (a value in m3/s is 3600 times smaller). If the model carries nothing, ASK THE USER rather than inventing one. Omit it only when nobody knows: the flow is then derived from the design velocity: the average velocity of the straight ducts between two branches equals it, none exceeds it by 20 %.","title":"Flow M3H"},"unit_name":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Only when the user asks about ONE unit or fan: its name, or a part of it - « CTA 12 », « AHU-Supply-L2 ». The tool looks it up among EVERY piece your rules gave the role centrale_de_traitement_d_air or ventilateur, case and accents ignored, all words required. Several matches: all are computed - except beyond 50 air networks, where nothing is computed and the matches come back: send the exact name of one. No match: it is matched like 'units' (close spellings, same numbers); still nothing: NOTHING is computed, and the list comes back with the closest names. Not with start_guid.","title":"Unit Name"},"units":{"anyOf":[{"items":{"type":"string"},"type":"array"},{"type":"null"}],"default":null,"description":"Air handling units or fans to compute, by name - from 'centrales_et_ventilateurs' of the list answer, or from 'equipements' of apply_ifc_rules. For each network connected to each of them, the longest path is computed. Send the EXACT names when you can: the tool also accepts all the words of a name (« CTA 12 »), a modeller's abbreviation and close spellings - but only with the SAME numbers. Not with start_guid. Beyond 50 air networks: ONE name per call.","title":"Units"},"all_networks":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True computes EVERY unit and fan of the list: the longest path of each network connected to them. Networks connected to no unit are not computed - the user traces them on the calculation page, or gives one of their pieces (network_guid). Offered only when the list answer says 'tous_possible': 50 air networks or fewer, units connected. Use it when the user asked for the whole model or ticked 'Tous'. Refused beyond 50 air networks: that model is computed one unit at a time.","title":"All Networks"},"preliminary_design":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"True when the network is still at a PRELIMINARY stage - not sized yet. Every stretch then carries what its own ducts carry at the design velocity (the flow may rise along the circuit, which a sized network would forbid), and every fitting is computed at that velocity; the flow given at the unit is ignored. This is the ONLY mode where the tool returns pressure drops: they say what a correctly sized circuit with these singularities and this length would reach, not what this network loses. ASK THE USER which of the two they want before calling - see the two modes in this tool's description. Omit it for the normal calculation.","title":"Preliminary Design"},"excluded_guids":{"anyOf":[{"items":{"type":"string"},"type":"array"},{"type":"null"}],"default":null,"description":"Parts to close, by GlobalId. Closing a part cuts the walk there: whatever was only reached through it leaves the survey. Use it when the network visibly runs too far - through a plenum shared with another installation, for instance.","title":"Excluded Guids"}},"required":["token"],"title":"trace_duct_circuitsArguments"},"annotations":{"title":"Duct circuits of the air handling units and fans, computed for the pressure-drop page","readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"6be441297fb02c55a7e4a8baa7ecd3114f32a005c2ddf9d21fb95e431830e35c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"},{"serverName":"com.thenewengineer/hvac","endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","name":"water_content_from_vessel","title":null,"description":"DETERMINISTIC: the same inputs always give the same result — from\nany AI, on any day. Figures come from the standard's tables and\nformulas, never from a language model's estimate. Every step is\nauditable.\n\nDeduce the water content of an installation from the expansion vessel\nalready fitted.\n\nWHAT THIS IS FOR. Refurbishment, and site visits with no drawings.\nSizing a new vessel, a new pump or a new generator needs the water\ncontent, and on an existing installation nobody has it: the drawings\nare lost, or never matched what was built. The vessel on the wall is\nthe one piece of evidence still standing, and it was chosen from that\nvery figure.\n\nASK THE OPERATOR FIRST. Whoever filled or refilled the system knows\nthe real figure — from the meter, the filling station, or the\nmaintenance log — and that figure beats any deduction. This tool is\nwhat you use when nobody knows, or to check a number that looks\nwrong. It gets the conversation moving; it does not close it.\n\nHOW. The sizing calculation is run backwards: a trial water content is\nfed to the EN 12828 sizing, the resulting vessel is compared with the\none on site, and the trial is adjusted until they match. The formulas\nare never rewritten in reverse — the answer cannot contradict the\ndirect calculation, because it is the same code.\n\nWHAT THE ANSWER IS WORTH. A vessel is picked from a catalogue range:\na 200 L unit covers everything needing between 141 and 200 L. The\nresult is therefore A RANGE, never a single figure. And an oversized\nvessel — common — will overstate the content. Compare the range with\nwhat you see on site; it does not replace looking.\n\nIt also assumes the vessel was sized correctly in the first place. If\nit was not, the deduction inherits the mistake — which is itself\nworth knowing: a range far from what the installation plainly holds\nmeans the vessel is wrong, and that is a finding in its own right.\n","inputSchema":{"type":"object","properties":{"vessel_volume_l":{"description":"Nominal capacity of the expansion vessel actually installed, in litres — read it on the nameplate.","exclusiveMinimum":0,"maximum":100000,"title":"Vessel Volume L","type":"number"},"flow_temperature_c":{"anyOf":[{"maximum":200,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"Design flow temperature, °C. In heating this is the highest the water reaches.","title":"Flow Temperature C"},"return_temperature_c":{"anyOf":[{"maximum":200,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"Design return temperature, °C.","title":"Return Temperature C"},"pressurisation":{"default":"static","description":"How pressure is held: 'static' for a plain membrane vessel, 'compressor' for a compressor unit (Compresso and the like), 'pump' for a pump unit. A compressor or pump unit holds the pressure itself, so height and valve setting play no part.","title":"Pressurisation","type":"string"},"static_height_m":{"anyOf":[{"maximum":300,"minimum":0,"type":"number"},{"type":"null"}],"default":null,"description":"Height of the highest point above the vessel, in metres. Required for 'static' only — a compressor or pump unit does not use it.","title":"Static Height M"},"valve_setting_bar":{"anyOf":[{"exclusiveMinimum":0,"maximum":25,"type":"number"},{"type":"null"}],"default":null,"description":"Safety valve setting, bar. Required for 'static' only.","title":"Valve Setting Bar"},"fill_temperature_c":{"anyOf":[{"maximum":100,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"Temperature the water was at when the system was filled, °C. 10 °C is the usual mains temperature indoors. Ask, or state the assumption.","title":"Fill Temperature C"},"min_temperature_c":{"anyOf":[{"maximum":100,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"LOWEST temperature the fluid can reach, °C — including a breakdown, not just normal running. Indoors, 10 °C. Outdoors, 0 °C, or down to the freezing point of the glycol mix. This is what fixes the reference volume.","title":"Min Temperature C"},"max_temperature_c":{"anyOf":[{"maximum":250,"minimum":-50,"type":"number"},{"type":"null"}],"default":null,"description":"HIGHEST temperature the fluid can reach, °C — in extreme conditions, running OR stopped. In heating it is the flow temperature. In cooling it is not the regime at all: a stopped chiller lets the water warm to ambient — 40 °C outdoors, 30 °C indoors in a temperate climate. This is what fixes the expansion.","title":"Max Temperature C"},"fluid":{"default":"water","description":"Heat-transfer fluid: 'eau' (Water), 'meg' (MEG), 'mpg' (MPG), 'tyfocor' (TYFOCOR L (MPG)).","title":"Fluid","type":"string"},"glycol_percent":{"default":0,"description":"Glycol concentration in %, ignored for water.","maximum":60,"minimum":0,"title":"Glycol Percent","type":"number"},"installation":{"default":"heating","description":"'heating' or 'cooling'.","title":"Installation","type":"string"}},"required":["vessel_volume_l"],"title":"water_content_from_vesselArguments"},"annotations":{"title":"WATER CONTENT from the vessel already installed (EN 12828 reversed) — deterministic","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"5cde1f99c5771af23e0799f4ed66ee1743af896d2f185c4ce1e27b6484121a33","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-17T05:46:12.429Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"861cd7e974dc41342c00daf361c45ac04b5093d9c21793b6b239f3bf5c6dd5df","protocol":"streamable-http","status":"indexed","toolCount":11,"observedAt":"2026-11-17T05:46:12.429Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"com.thenewengineer/hvac":{"url":"https://thenewengineer.com/mcp"}}},"Cursor":{"mcpServers":{"com.thenewengineer/hvac":{"url":"https://thenewengineer.com/mcp"}}},"VS Code":{"servers":{"com.thenewengineer/hvac":{"type":"http","url":"https://thenewengineer.com/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://thenewengineer.com/mcp"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:com.thenewengineer%2Fhvac","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/com.thenewengineer%2Fhvac","name":"com.thenewengineer/hvac","description":"IFC models: duct networks, circuits, pressure drop. EN 12828 vessels, EN 378, Swiss refrigerants.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://thenewengineer.com/mcp"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://thenewengineer.com/ai","repositoryUrl":null,"version":"1.3.0"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"com.thenewengineer/hvac","status":"online","lastCheckedAt":"2026-11-20T08:17:14.655Z","lastSuccessfulCheck":"2026-11-20T08:17:14.655Z","latencyMs":301,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T08:17:14.655Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T08:17:14.655Z"},"security":null,"timestamps":{"createdAt":"2026-10-10T15:34:24.120Z","updatedAt":"2026-10-10T15:34:24.120Z","observedAt":"2026-11-20T08:17:14.655Z"},"compatibility":{"serverVersion":"1.3.0","protocolVersions":[{"protocol":"mcp","version":null}]}}}}