Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_ceiling_floor_vent

Add a vertical flow vent connecting a top compartment's floor to a bottom compartment's ceiling, or to outside. Specify compartments, vent area, type, and shape.

Instructions

Add a ceiling/floor vent (vertical flow opening) between compartments.

Vertical flow vents connect compartments stacked in elevation, or a compartment to the outside (e.g. a hole in a roof). Both compartments must already exist in the model; comp_bottom may be "OUTSIDE".

Parameters

model_id : str Id of the model to modify. id : str Unique name of the vent. comp_top : str Top compartment id, where the vent is in the floor. comp_bottom : str Bottom compartment id, where the vent is in the ceiling, or "OUTSIDE" for the exterior. area : float Cross-sectional area of the vent opening. Default units: m². type : str, optional Type of ceiling/floor vent: FLOOR or CEILING. Default value: FLOOR. shape : str, optional Shape factor used to compute the effective diameter and flow coefficients: ROUND or SQUARE. Default value: ROUND. 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 upper compartment. Default units: m, default value: [0, 0] m.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
areaYes
typeNoFLOOR
shapeNoROUND
offsetsNo
comp_topYes
model_idYes
comp_bottomYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations present, but the description covers what the tool does (adds a vent), parameters with defaults, and return value (confirmation, model summary, warnings). Lacks explicit mention of side effects or destructive actions, but given the nature, it is adequate.

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?

Well-structured docstring with sections for description, parameters, and returns. Each sentence adds value, no redundancy. Appropriate length for the complexity.

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?

Covers all 8 parameters (5 required) with units and defaults, explains use case (vertical flow), specifies prerequisites (compartments exist), and describes return type. Complete given no annotations and no output schema in structured data.

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 has 0% description coverage, but the description provides detailed parameter documentation including units, defaults, allowed values (e.g., FLOOR/CEILING, ROUND/SQUARE), and clarifies that offsets are for visualization only. Adds full meaning beyond schema titles.

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 it adds a ceiling/floor vent (vertical flow opening) between compartments. It distinguishes from siblings like add_wall_vent (horizontal) and add_mechanical_vent (mechanical) by specifying vertical orientation.

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 context that vents connect stacked compartments or a compartment to outside, and that compartments must exist. Does not explicitly mention when not to use or give equivalent tools, but the vertical vs horizontal distinction is implied.

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