Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_compartment

Add a compartment with specified dimensions to a CFAST fire model. Optionally assign surface materials for ceiling, walls, and floor.

Instructions

Add a compartment to a model.

Any surface material id given (ceiling, wall, floor) must already exist in the model — add it first with add_material. If the thermophysical properties of a surface are not included, CFAST treats it as adiabatic (no heat transfer).

Parameters

model_id : str Id of the model to modify. id : str Unique alphanumeric name of the compartment, referenced later by fires and wall vents. width : float Width of the compartment as measured on the X axis from its origin. Default units: m. depth : float Depth of the compartment as measured on the Y axis from its origin. Default units: m. height : float Height of the compartment as measured on the Z axis from its origin. Default units: m. ceiling_mat_id : str or None, optional Material id defining the ceiling surface. Default value: Off. ceiling_thickness : float or None, optional Thickness of the ceiling surface. Default units: m, default value: thickness of the material. wall_mat_id : str or None, optional Material id defining the wall surfaces. Default value: Off. wall_thickness : float or None, optional Thickness of the wall surfaces. Default units: m, default value: thickness of the material. floor_mat_id : str or None, optional Material id defining the floor surface. Default value: Off. floor_thickness : float or None, optional Thickness of the floor surface. Default units: m, default value: thickness of the material. origin_x : float, optional Absolute x coordinate of the lower, left, front corner of the room. Negative values are not allowed. Default units: m, default value: 0.0 m. origin_y : float, optional Absolute y coordinate of the lower, left, front corner of the room. Negative values are not allowed. Default units: m, default value: 0.0 m. origin_z : float, optional Height of the floor of the compartment with respect to the station elevation. Default units: m, default value: 0.0 m.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
depthYes
widthYes
heightYes
model_idYes
origin_xNo
origin_yNo
origin_zNo
wall_mat_idNo
floor_mat_idNo
ceiling_mat_idNo
wall_thicknessNo
floor_thicknessNo
ceiling_thicknessNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses key behaviors: material defaults, units, negative value restrictions for origins, and the return type. It lacks some details like error handling but is transparent overall.

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 a brief intro and detailed parameter list. While it is relatively long, every sentence adds value and is appropriately front-loaded. Slightly more conciseness could be achieved, but it is effective.

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 14 parameters, lack of annotations, and the presence of an output schema, the description covers prerequisites, default behaviors, constraints, and return values. It is complete and leaves no significant gaps for an AI agent.

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%, but the description provides extensive explanations for all 14 parameters, including defaults, units, constraints, and meaning. This fully compensates for the lack of schema descriptions.

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 'Add a compartment to a model.' It also distinguishes from sibling tools like add_material by noting that surface materials must exist first and can be added with add_material.

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 provides explicit usage guidelines, such as requiring surface materials to exist beforehand and the default adiabatic behavior. It does not explicitly state when not to use the tool, but the context is clear.

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