Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

update_compartment

Update a compartment's dimensions, origin, or surface materials by specifying only the parameters to change, leaving others unchanged.

Instructions

Update parameters of an existing compartment.

Selects the compartment by comp_id and changes only the parameters you provide; any left as None is unchanged. Use this to attach surface materials to the first compartment (created bare by create_model) or to revise any compartment later. Any surface material id given must already exist in the model — add it first with add_material. The compartment's id itself is the selector and is not changed here.

Parameters

model_id : str Id of the model to modify. comp_id : str Id of the compartment to update. width : float or None, optional New width of the compartment as measured on the X axis from its origin. Default units: m. None leaves it unchanged. depth : float or None, optional New depth of the compartment as measured on the Y axis from its origin. Default units: m. None leaves it unchanged. height : float or None, optional New height of the compartment as measured on the Z axis from its origin. Default units: m. None leaves it unchanged. ceiling_mat_id : str or None, optional Material id defining the ceiling surface. None leaves it unchanged. ceiling_thickness : float or None, optional Thickness of the ceiling surface. Default units: m. None leaves it unchanged. wall_mat_id : str or None, optional Material id defining the wall surfaces. None leaves it unchanged. wall_thickness : float or None, optional Thickness of the wall surfaces. Default units: m. None leaves it unchanged. floor_mat_id : str or None, optional Material id defining the floor surface. None leaves it unchanged. floor_thickness : float or None, optional Thickness of the floor surface. Default units: m. None leaves it unchanged. origin_x : float or None, optional Absolute x coordinate of the lower, left, front corner of the room. Negative values are not allowed. Default units: m. None leaves it unchanged. origin_y : float or None, optional Absolute y coordinate of the lower, left, front corner of the room. Negative values are not allowed. Default units: m. None leaves it unchanged. origin_z : float or None, optional Height of the floor of the compartment with respect to the station elevation. Default units: m. None leaves it unchanged.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
widthNo
heightNo
comp_idYes
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?

With no annotations, description carries full burden. It explains partial update behavior, constraints (negative origins not allowed, units in meters), and return type (string with confirmation and warnings). Lacks mention of side effects like model rebuild, but is otherwise transparent.

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 a summary paragraph followed by parameter list. Front-loaded with purpose. While the parameter list is long, it is necessary given the schema coverage. Could slightly reduce redundancy but overall efficient.

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 14 parameters, 2 required, and existence of output schema, the description covers selection logic, update behavior, constraints, parameter details, and return value. Leaves no critical gaps.

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, so description compensates fully. Details each parameter: width, depth, height, origins, material ids, thicknesses, with units, default (None leaves unchanged), and constraints (e.g., no negative origin_x/y).

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 'Update parameters of an existing compartment.' and explains that selection is by comp_id with partial update. It distinguishes from 'add_compartment' and other update tools, making the purpose unambiguous.

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: use to attach surface materials to first compartment created bare by create_model, or revise any compartment. Warns that material ids must exist (use add_material). No explicit when-not-to-use, but sufficient guidance for the main use case.

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