Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

add_surface_connection

Add a surface connection between compartments to model heat transfer through walls or floors. Specify compartments, connection type, and fraction for wall connections.

Instructions

Add a surface connection between compartments.

Surface connections transfer heat through solid boundaries between two compartments. Both compartments must already exist in the model. Unlike other components, a surface connection has no id; refer to it by its position (index) when updating. For WALL connections you should add one in each direction (comp_id -> comp_ids and comp_ids -> comp_id).

Parameters

model_id : str Id of the model to modify. conn_type : str Type of connection: WALL for horizontal heat transfer through vertical surfaces, FLOOR for vertical heat transfer through horizontal surfaces. comp_id : str First compartment id. For WALL, the compartment whose wall area fraction is given; for FLOOR, the top compartment (through its floor). comp_ids : str Second compartment id. For FLOOR, the bottom compartment (through its ceiling). fraction : float or None, optional Fraction (0-1) of the first compartment's vertical surface area that connects the two compartments. Required for WALL connections; must be None for FLOOR connections.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comp_idYes
comp_idsYes
fractionNo
model_idYes
conn_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes key behavioral traits: heat transfer, id-less referencing, fraction constraints for WALL vs FLOOR. Could mention whether adding overwrites or duplicates connections.

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?

Well-structured with brief intro, parameter definitions, and return info. No wasted words.

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?

Covers purpose, prerequisites, parameters, and returns. Could mention any limits on number of connections or interactions with other components.

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?

All five parameters are described with detailed semantics, including constraints on fraction and role of comp_id/comp_ids for different connection types, compensating for 0% schema description 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?

Clear verb 'Add' and resource 'surface connection'. Explanation of heat transfer through solid boundaries distinguishes it from sibling tools like add_wall_vent or add_ceiling_floor_vent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (compartments must exist), gives directionality advice for WALL connections, and notes that no ID is used (refer by index).

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