Skip to main content
Glama
using76
by using76

bulc_set_fds_hvac

Destructive

Configure furniture as HVAC vents in BULC Building Designer by assigning supply or exhaust properties to specific faces for airflow simulation.

Instructions

Configure a furniture item as an FDS HVAC (supply or exhaust vent). Assigns surface properties to specific faces of the obstruction. Supply vents blow air in, exhaust vents extract air out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to configure as HVAC
surfacesNoSurface assignment for each face. Keys: minX, maxX, minY, maxY, minZ, maxZ. Values: 'INERT', 'supply', or 'exhaust'. Example: {maxZ: 'supply'}
flowTypeNoFlow specification type: 'volume' (m³/s) or 'velocity' (m/s). Default: velocity
flowValueNoFlow value (volume in m³/s or velocity in m/s). Default: 4.0
temperatureNoSupply air temperature in Celsius (supply only). Default: 20
surfaceIdNoCustom surface ID. Default: auto-generated

Implementation Reference

  • Handler logic for the 'bulc_set_fds_hvac' tool: validates input parameters using SetHvacSchema and sends a 'set_fds_hvac' command to the BULC client.
    case "bulc_set_fds_hvac": {
      const validated = SetHvacSchema.parse(args);
      result = await client.sendCommand({
        action: "set_fds_hvac",
        params: validated,
      });
      break;
  • Zod validation schema (SetHvacSchema) for the input parameters of the 'bulc_set_fds_hvac' tool.
    const SetHvacSchema = z.object({
      furnitureId: z.string(),
      surfaces: z.object({
        minX: z.enum(["INERT", "supply", "exhaust"]).optional(),
        maxX: z.enum(["INERT", "supply", "exhaust"]).optional(),
        minY: z.enum(["INERT", "supply", "exhaust"]).optional(),
        maxY: z.enum(["INERT", "supply", "exhaust"]).optional(),
        minZ: z.enum(["INERT", "supply", "exhaust"]).optional(),
        maxZ: z.enum(["INERT", "supply", "exhaust"]).optional(),
      }).optional(),
      flowType: z.enum(["volume", "velocity"]).optional(),
      flowValue: z.number().optional(),
      temperature: z.number().optional(),
      surfaceId: z.string().optional(),
    });
  • MCP tool registration for 'bulc_set_fds_hvac', including name, description, inputSchema, and annotations.
    {
      name: "bulc_set_fds_hvac",
      description:
        "Configure a furniture item as an FDS HVAC (supply or exhaust vent). " +
        "Assigns surface properties to specific faces of the obstruction. " +
        "Supply vents blow air in, exhaust vents extract air out.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to configure as HVAC",
          },
          surfaces: {
            type: "object",
            description: "Surface assignment for each face. Keys: minX, maxX, minY, maxY, minZ, maxZ. " +
              "Values: 'INERT', 'supply', or 'exhaust'. Example: {maxZ: 'supply'}",
            properties: {
              minX: { type: "string", enum: ["INERT", "supply", "exhaust"] },
              maxX: { type: "string", enum: ["INERT", "supply", "exhaust"] },
              minY: { type: "string", enum: ["INERT", "supply", "exhaust"] },
              maxY: { type: "string", enum: ["INERT", "supply", "exhaust"] },
              minZ: { type: "string", enum: ["INERT", "supply", "exhaust"] },
              maxZ: { type: "string", enum: ["INERT", "supply", "exhaust"] },
            },
          },
          flowType: {
            type: "string",
            description: "Flow specification type: 'volume' (m³/s) or 'velocity' (m/s). Default: velocity",
            enum: ["volume", "velocity"],
          },
          flowValue: {
            type: "number",
            description: "Flow value (volume in m³/s or velocity in m/s). Default: 4.0",
          },
          temperature: {
            type: "number",
            description: "Supply air temperature in Celsius (supply only). Default: 20",
          },
          surfaceId: {
            type: "string",
            description: "Custom surface ID. Default: auto-generated",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:84-93 (registration)
    Routing registration in the main MCP server handler that dispatches calls to 'bulc_set_fds_hvac' (and other FDS data tools) to the specific handleFdsDataTool function.
    if (
      name === "bulc_get_fds_data" ||
      name === "bulc_set_fds_fire_source" ||
      name === "bulc_set_fds_detector" ||
      name === "bulc_set_fds_sprinkler" ||
      name === "bulc_set_fds_hvac" ||
      name === "bulc_set_fds_thermocouple" ||
      name === "bulc_clear_fds_data"
    ) {
      return await handleFdsDataTool(name, safeArgs);
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, confirming this is a write operation that modifies data. The description adds valuable context beyond annotations: it explains the functional difference between supply and exhaust vents ('Supply vents blow air in, exhaust vents extract air out'), which helps the agent understand the behavioral impact of surface assignments. However, it doesn't mention potential side effects like overwriting existing configurations or rate limits.

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 front-loaded with the core purpose and efficiently explains key concepts (supply vs. exhaust) in two sentences. No redundant information is present, though it could be slightly more structured by explicitly mentioning parameter roles.

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

Completeness3/5

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

For a destructive configuration tool with no output schema, the description is adequate but has gaps. It covers the purpose and basic behavior but lacks details on error conditions, what happens on success (e.g., confirmation message), or how changes propagate in the system. Given the complexity (6 parameters, nested objects), more context would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters are documented in the schema. The description adds minimal semantic value beyond the schema—it mentions 'surface properties' and 'specific faces' but doesn't elaborate on parameter interactions or usage examples. Baseline 3 is appropriate as the schema carries the documentation burden.

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 specific action ('Configure a furniture item as an FDS HVAC'), identifies the resource ('furniture item'), and distinguishes from siblings by specifying it's for HVAC vents (supply/exhaust) rather than other FDS components like detectors, fire sources, or sprinklers listed in sibling tools.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives is provided. While it distinguishes itself from other FDS tools by focusing on HVAC, it doesn't mention prerequisites (e.g., furniture must exist), exclusions, or compare with similar configuration tools like bulc_set_fds_detector or bulc_set_fds_sprinkler.

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/using76/BULC_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server