Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_fire

Add a time-dependent fire to an existing compartment in a CFAST fire model, including HRR, location, and fuel composition.

Instructions

Add a fire to a compartment of a model.

A fire in CFAST is specified via a time-dependent heat release rate (HRR). The compartment comp_id must already exist in the model. Fire properties are linearly interpolated between specified time points; if the simulation time is longer than the total duration of the fire, the final values are continued until the end of the simulation.

Parameters

model_id : str Id of the model to modify. id : str Unique name of the fire instance. comp_id : str Name of the compartment where the fire occurs. fire_id : str Unique name of the fire definition (fuel composition and HRR curve). May be the same as id. location : list[float] Position [x, y] of the center of the base of the fire relative to the front left corner of the compartment. Default units: m. data_table : list[list[float]] Time-dependent fire properties: one row per time point, with columns [TIME (s), HRR (kW), HEIGHT (m), AREA (m²), CO_YIELD, SOOT_YIELD, HCN_YIELD, HCL_YIELD, TRACE_YIELD], yields in kg/kg. Example for a fire growing to 1000 kW at 300 s: [[0, 0, 0, 0.3, 0.005, 0.02, 0, 0, 0], [300, 1000, 0, 0.3, 0.005, 0.02, 0, 0, 0]]. carbon : float, optional Number of carbon atoms in the fuel molecule. Default value: 1. chlorine : float, optional Number of chlorine atoms in the fuel molecule; assumed to completely react to form HCl. Default value: 0. hydrogen : float, optional Number of hydrogen atoms in the fuel molecule. Default value: 4. nitrogen : float, optional Number of nitrogen atoms in the fuel molecule; assumed to completely react to form HCN. Default value: 0. oxygen : float, optional Number of oxygen atoms in the fuel molecule. Default value: 0. heat_of_combustion : float, optional The energy released per unit mass of fuel consumed. Default units: kJ/kg, default value: 50000 kJ/kg. radiative_fraction : float, optional The fraction of the combustion energy that is emitted in the form of thermal radiation. Default units: none, default value: 0.35.

Returns

str Confirmation, the updated model summary, and any warnings (for example a fire located outside the compartment footprint).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
carbonNo
oxygenNo
comp_idYes
fire_idYes
chlorineNo
hydrogenNo
locationYes
model_idYes
nitrogenNo
data_tableYes
heat_of_combustionNo
radiative_fractionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries full burden and delivers thorough behavioral details: time-dependent HRR specification, linear interpolation, continuation of final values, and warning if fire is outside compartment. No contradictions.

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 well-structured with sections for parameters and return value, using bullet points and an example. While lengthy, every sentence adds value given the tool's complexity, earning its place.

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 complexity (13 parameters, complex nested data type), the description covers all parameters, explains the return value, and warns about edge cases. No gaps remain despite the absence of annotations.

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%, yet the description provides detailed explanations for all 13 parameters, including defaults, units, and an explicit example for the complex 'data_table' parameter. This adds significant meaning beyond the schema's type information.

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 action ('Add') and resource ('fire') and specifies the context of adding to a compartment of a model. It distinguishes the tool from the sibling 'update_fire' by indicating this is for new additions.

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 important context: the compartment must already exist, simulation interpolation behavior, and continuation of fire properties. However, it does not explicitly mention when to use this tool versus the sibling 'update_fire' or other alternatives.

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