Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_mechanical_vent

Add a mechanical vent with constant volumetric flow between two compartments or to the outside. Specify flow rate, duct geometry, and pressure cutoffs for fan ventilation.

Instructions

Add a mechanical vent between two compartments.

Mechanical ventilation moves air at a user-specified volume flow between two compartments, or between a compartment and the outside. Both compartments must already exist in the model; comp_from or comp_to may be "OUTSIDE".

Parameters

model_id : str Id of the model to modify. id : str Unique name of the mechanical ventilation system. comp_from : str Compartment from which the fan flow originates, or "OUTSIDE". comp_to : str Compartment to which the fan flow terminates, or "OUTSIDE". flow : float Constant volumetric flow rate of the fan. Default units: m³/s. area : list[float] or None, optional Cross-sectional area of the opening for each connection [area_from, area_to]. Default units: m², default value: [0, 0] m². heights : list[float] or None, optional Height of the midpoint of the duct opening above the floor for each connection [height_from, height_to]. Default units: m, default value: [0, 0] m. orientations : list[str] or None, optional Flow orientation for each connection, HORIZONTAL or VERTICAL. A horizontal diffuser implies vertical flow through the ceiling or floor; a vertical diffuser implies horizontal flow through a wall. Default value: ["VERTICAL", "VERTICAL"]. cutoffs : list[float] or None, optional Pressure control values [begin_drop_off_pressure, zero_flow_pressure]: above the first the flow drops off, above the second it is zero. Default units: Pa, default value: [200, 300] Pa. offsets : list[float] or None, optional For visualization only, [x_offset, y_offset] horizontal distances between the center of the vent and the origin of the X and Y axes in the first compartment. Default units: m, default value: [0, 0] m. filter_time : float, optional Time at which mechanical vent filtering begins. Default units: s, default value: 0 s. filter_efficiency : float, optional Portion of soot and trace species mass removed from the flow, specified as a percentage (0-100). Default value: 0.

Returns

str Confirmation, the updated model summary, and any warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
areaNo
flowYes
comp_toYes
cutoffsNo
heightsNo
offsetsNo
model_idYes
comp_fromYes
filter_timeNo
orientationsNo
filter_efficiencyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains parameters and return value but does not disclose side effects, error conditions, or whether the operation is reversible. Lacks behavioral details like model mutation implications.

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?

Structured with Parameters and Returns sections, front-loads purpose. Slightly verbose in parameter descriptions but each sentence provides necessary information. Efficient overall.

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?

For a complex 12-parameter tool with no annotations and no output schema (description provides return type), the description covers purpose, all parameters, and return value. Adequately complete.

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

Parameters5/5

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

Schema description coverage is 0%, so description fully compensates. Each parameter is described with units, defaults, valid options (e.g., 'OUTSIDE'), and meaning, adding significant value beyond the schema.

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 clearly states the verb 'Add' and resource 'mechanical vent', specifies it is between two compartments or between a compartment and outside, and distinguishes from sibling vent tools by mentioning mechanical (fan-forced) ventilation.

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?

Provides precondition that compartments must exist and allows 'OUTSIDE', but does not explicitly state when to use this vs other vent types (e.g., natural vents). Offers some context but no exclusions or named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bewygs/cfast-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server