Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

create_model

Initialize a new CFAST fire simulation by defining the first compartment's dimensions, title, and optional environmental parameters, then get a model ID for subsequent configuration and execution.

Instructions

Create a new CFAST model with its first compartment and register it.

A CFAST model must contain at least one compartment, so creation includes the first one. Add materials, further compartments, wall vents and fires with the add_* tools, then use inspect_model and run_model.

Parameters

title : str Title of the simulation. May consist of letters, numbers, and/or symbols and may be up to 50 characters. room_id : str Unique alphanumeric name of the first compartment, referenced later by fires and wall vents. room_width : float Width of the compartment as measured on the X axis from its origin. Default units: m. room_depth : float Depth of the compartment as measured on the Y axis from its origin. Default units: m. room_height : float Height of the compartment as measured on the Z axis from its origin. Default units: m. time_simulation : int, optional Length of time over which the simulation takes place. Default units: s, default value: 900 s. interior_temperature : float, optional Initial ambient temperature inside the structure. Default units: °C, default value: 20 °C. exterior_temperature : float, optional Initial ambient temperature outside the structure. Default units: °C, default value: 20 °C. relative_humidity : float, optional Initial relative humidity, only specified for the interior. Default units: % RH, default value: 50 %.

Returns

str The new model_id, the model summary, and any warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
room_idYes
room_depthYes
room_widthYes
room_heightYes
time_simulationNo
relative_humidityNo
exterior_temperatureNo
interior_temperatureNo

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 discloses that the tool creates and registers the model, includes the first compartment, and returns model_id, summary, and warnings. It does not mention permissions or side effects, but for a creation tool, this is adequate transparency.

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?

The description is efficiently structured with a brief introductory paragraph, a clean parameter list with units and defaults, and a return value section. Every sentence adds value, and the length is appropriate for the tool's 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?

Given the 9 parameters (5 required) and no annotations or output schema description, the description fully covers the workflow, parameter details, and return type. It explains the creation process and next steps, making it complete for an agent to use correctly.

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 detailed semantics for each parameter: title constraints (max 50 chars, letters/numbers/symbols), room_id uniqueness, default units for dimensions (m), default values for optional parameters (time_simulation: 900 s, etc.). This adds substantial meaning 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 tool creates a new CFAST model with its first compartment and registers it, using the specific verb 'Create' and resource 'CFAST model'. It distinguishes from sibling tools by mentioning the workflow of using add_* tools for further elements.

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 explains that creation includes the first compartment because a model must contain at least one, and advises to use add_* tools for additional elements, then inspect_model and run_model. It provides clear context for usage but could explicitly state when not to use this tool.

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