Skip to main content
Glama
using76
by using76

bulc_set_fds_fire_source

Destructive

Configure furniture as a fire source in FDS simulations using HRRPUA mode with time-based ramping. Calculates heat release rate based on the furniture's surface area.

Instructions

Configure a furniture item as an FDS fire source. Supports HRRPUA (Heat Release Rate Per Unit Area) mode with time-based ramping. The fire will use the furniture's surface area for HRR calculations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to configure as fire source
hrrpuaNoHeat Release Rate Per Unit Area in kW/m². Default: 500
surfaceIdNoCustom surface ID. Default: auto-generated
colorNoSurface color. Options: RED, ORANGE, YELLOW. Default: RED
rampNoTime-based ramp function as array of [time, fraction] pairs. Example: [[0, 0], [10, 0.5], [60, 1.0], [120, 1.0], [180, 0]]
tauQNot-squared fire growth coefficient (optional, uses ramp if not set)

Implementation Reference

  • Executes the tool by validating the input parameters with Zod's SetFireSourceSchema and forwarding a 'set_fds_fire_source' command to the BULC client for actual implementation.
    case "bulc_set_fds_fire_source": {
      const validated = SetFireSourceSchema.parse(args);
      result = await client.sendCommand({
        action: "set_fds_fire_source",
        params: validated,
      });
      break;
    }
  • Zod schema for input validation of the 'bulc_set_fds_fire_source' tool parameters.
    const SetFireSourceSchema = z.object({
      furnitureId: z.string(),
      hrrpua: z.number().positive().optional(),
      surfaceId: z.string().optional(),
      color: z.enum(["RED", "ORANGE", "YELLOW"]).optional(),
      ramp: z.array(z.array(z.number()).length(2)).optional(),
      tauQ: z.number().optional(),
    });
  • MCP tool schema definition for 'bulc_set_fds_fire_source', including description, input schema, and annotations for the tool listing.
    {
      name: "bulc_set_fds_fire_source",
      description:
        "Configure a furniture item as an FDS fire source. " +
        "Supports HRRPUA (Heat Release Rate Per Unit Area) mode with time-based ramping. " +
        "The fire will use the furniture's surface area for HRR calculations.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to configure as fire source",
          },
          hrrpua: {
            type: "number",
            description: "Heat Release Rate Per Unit Area in kW/m². Default: 500",
          },
          surfaceId: {
            type: "string",
            description: "Custom surface ID. Default: auto-generated",
          },
          color: {
            type: "string",
            description: "Surface color. Options: RED, ORANGE, YELLOW. Default: RED",
          },
          ramp: {
            type: "array",
            description: "Time-based ramp function as array of [time, fraction] pairs. " +
              "Example: [[0, 0], [10, 0.5], [60, 1.0], [120, 1.0], [180, 0]]",
            items: {
              type: "array",
              items: { type: "number" },
            },
          },
          tauQ: {
            type: "number",
            description: "t-squared fire growth coefficient (optional, uses ramp if not set)",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:84-94 (registration)
    Tool dispatch registration in the main MCP server: routes calls to 'bulc_set_fds_fire_source' to the 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, which the description aligns with by implying configuration changes. The description adds valuable context beyond annotations: it specifies that the fire uses the furniture's surface area for calculations and supports HRRPUA mode with ramping, which are behavioral details not covered by annotations. However, it lacks information on permissions, side effects, or error handling.

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 front-loaded with the core purpose in the first sentence, followed by supporting details in a second sentence. Both sentences are essential, with no redundant information, making it highly efficient and well-structured.

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?

Given the destructive nature (annotations), 6 parameters, and no output schema, the description is adequate but incomplete. It covers the tool's function and key behavioral aspects but lacks details on outcomes, error conditions, or integration with other tools, which could hinder an agent's understanding in a complex simulation context.

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?

With 100% schema description coverage, the input schema fully documents all 6 parameters. The description adds minimal semantic value, only hinting at the purpose of 'hrrpua' and 'ramp' in the context of fire configuration. It doesn't explain parameter interactions or provide examples beyond what's in the schema, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Configure a furniture item as an FDS fire source') and specifies the mode ('HRRPUA mode with time-based ramping'), which distinguishes it from other fire-related tools like 'bulc_set_fds_sprinkler' or 'bulc_set_fds_thermocouple'. However, it doesn't explicitly differentiate from all siblings, such as 'bulc_set_fire_coupling', which might also involve fire configuration.

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?

The description provides no guidance on when to use this tool versus alternatives, such as other fire-setting tools in the sibling list. It mentions the mode (HRRPUA) but doesn't specify prerequisites, exclusions, or comparative contexts, leaving the agent without clear usage direction.

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