Skip to main content
Glama
bewygs

CFAST MCP

by bewygs

update_wall_vent

Update an existing wall vent's parameters such as connection compartments, position, and dimensions. Specify only the fields to change; unchanged fields remain as before.

Instructions

Update an existing wall vent.

Selects the vent by vent_id and changes only the parameters you provide; any left as None is unchanged. The vent's id is the selector and is not changed here.

Parameters

model_id : str Id of the model to modify. vent_id : str Id of the wall vent to update. comp_a : str or None, optional First compartment id; the reference for all vent specifications. To change the connection, provide both comp_a and comp_b. None leaves the connection unchanged. comp_b : str or None, optional Second compartment id, or "OUTSIDE" for the exterior. To change the connection, provide both comp_a and comp_b. None leaves the connection unchanged. bottom : float or None, optional Position of the bottom of the opening relative to the floor of the first compartment. Default units: m. None leaves it unchanged. height : float or None, optional Height of the opening relative to the bottom of the opening. Default units: m. None leaves it unchanged. width : float or None, optional Width of the opening. Default units: m. None leaves it unchanged. face : str or None, optional The wall on which the vent is positioned: FRONT, REAR, LEFT or RIGHT. None leaves it unchanged. offset : float or None, optional For visualization only, the horizontal distance between the near edge of the vent and the origin of the axis defined by the selected face. Default units: m. None leaves it unchanged.

Returns

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faceNo
widthNo
bottomNo
comp_aNo
comp_bNo
heightNo
offsetNo
vent_idYes
model_idYes

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 carries full burden. It discloses that the tool performs partial updates, the vent_id is unchanged, and returns confirmation and warnings. It lacks details on side effects, permissions, or reversibility, but is adequate.

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 a brief overview, parameter list, and return value. It is concise, front-loaded, and every sentence is informative without redundancy.

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 9 parameters, no annotations, and an output schema mentioned, the description covers purpose, behavior, parameter details, and return format completely. There are no obvious gaps for an AI agent to use the tool 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 coverage is 0%, but the description provides detailed semantics for each parameter: purpose, behavior on None, and constraints (e.g., both comp_a and comp_b needed for connection change). This adds significant value 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 uses a specific verb 'Update' and resource 'wall vent', clearly indicating the action. It differentiates from sibling tools like 'add_wall_vent' by focusing on modification. The mention of selecting by vent_id and partial update adds clarity.

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 states to use when updating an existing vent, with partial updates by leaving parameters as None. It implies not to use for creation (add_wall_vent) but lacks explicit alternatives or when-not-to-use statements.

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