Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_material

Add a material with thermal properties to a CFAST model for use in compartment surfaces or targets. Define conductivity, density, specific heat, thickness, and emissivity.

Instructions

Add a material to a model.

A compartment can reference this material by id for its ceiling, wall or floor surfaces, or a target.

Parameters

model_id : str Id of the model to modify, as returned by create_model. id : str A one-word (no more than 8 characters) unique identifier for the material, used in other inputs to reference it. material : str A descriptive name for the material. conductivity : float Thermal conductivity for the material. Default units: W/(m·K). density : float Density for the material. Default units: kg/m³. specific_heat : float Specific heat for the material. Default units: kJ/(kg·K). thickness : float Thickness of the material. Default units: m. emissivity : float, optional Emissivity of the material surface; the fraction of radiation that is absorbed by the material. Default units: none, default value: 0.9.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
densityYes
materialYes
model_idYes
thicknessYes
emissivityNo
conductivityYes
specific_heatYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like id uniqueness constraints, model mutation details, or side effects (e.g., overwriting existing material). Only parameter definitions are given.

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 structured with sections and bullet points, making it readable. While some repetition exists (e.g., parameter descriptions in docstring style), it is not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (context signal), the description's mention of return as confirmation/summary/warnings is sufficient. All 8 parameters are explained, and the overall context for adding a material is covered.

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?

The description adds significant value to each parameter beyond the schema: units for conductivity, density, specific heat, thickness; default value and units for emissivity; character limit for id. This compensates for the 0% schema coverage.

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 adds a material to a model, and mentions how compartments can reference it by ID. This distinguishes it from update_material, 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?

The description implicitly suggests using this tool before referencing materials in compartments or targets, but does not explicitly contrast with update_material or provide when-not-to-use guidance.

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