Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

update_mechanical_vent

Modify an existing mechanical vent in a CFAST fire model by updating its flow, area, height, orientation, cutoffs, offsets, or filter settings. Only parameters you specify are changed.

Instructions

Update an existing mechanical vent.

Selects the vent by vent_id and changes only the parameters you provide; any left as None is unchanged. The vent's id is the selector and is not changed here.

Parameters

model_id : str Id of the model to modify. vent_id : str Id of the mechanical vent to update. comp_from : str or None, optional Compartment from which the fan flow originates, or "OUTSIDE". To change the connection, provide both comp_from and comp_to. None leaves the connection unchanged. comp_to : str or None, optional Compartment to which the fan flow terminates, or "OUTSIDE". To change the connection, provide both comp_from and comp_to. None leaves the connection unchanged. flow : float or None, optional Constant volumetric flow rate of the fan. Default units: m³/s. None leaves it unchanged. area : list[float] or None, optional Cross-sectional area of the opening for each connection [area_from, area_to]. Default units: m². None leaves it unchanged. 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. None leaves it unchanged. orientations : list[str] or None, optional Flow orientation for each connection, HORIZONTAL or VERTICAL. None leaves it unchanged. cutoffs : list[float] or None, optional Pressure control values [begin_drop_off_pressure, zero_flow_pressure]. Default units: Pa. None leaves it unchanged. offsets : list[float] or None, optional For visualization only, [x_offset, y_offset]. Default units: m. None leaves it unchanged. filter_time : float or None, optional Time at which mechanical vent filtering begins. Default units: s. None leaves it unchanged. filter_efficiency : float or None, optional Portion of soot and trace species mass removed (0-100 %). None leaves it unchanged.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
flowNo
comp_toNo
cutoffsNo
heightsNo
offsetsNo
vent_idYes
model_idYes
comp_fromNo
filter_timeNo
orientationsNo
filter_efficiencyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description details parameter behavior (None leaves unchanged, connection requires both comp_from and comp_to) and return value (confirmation, summary, warnings). It lacks information on side effects or atomicity but covers core behavioral traits.

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 well-structured with an intro, parameter list, and returns section. It is fairly concise for 12 parameters, though some grouping could reduce repetition.

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

Completeness4/5

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

Given 12 parameters, 2 required, and an output schema, the description covers all parameters with usage context and return type. Minor gaps like validation constraints do not significantly impair completeness.

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 coverage is 0%, so the description provides comprehensive parameter semantics: type, meaning, default units, and usage notes (e.g., 'None leaves it unchanged', 'To change the connection, provide both'). This adds essential 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 states the tool updates an existing mechanical vent, selects by vent_id, and only changes provided parameters. This is a specific verb+resource that clearly distinguishes it from sibling tools like add_mechanical_vent.

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 clearly indicates when to use the tool (updating existing vents) and implies creation is done via add_mechanical_vent. However, it does not explicitly state when not to use or list alternative tools.

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