Skip to main content
Glama
using76
by using76

bulc_set_fds_sprinkler

Destructive

Configure furniture as an FDS sprinkler for fire suppression simulation by setting thermal response parameters and water spray characteristics.

Instructions

Configure a furniture item as an FDS sprinkler. Uses RTI and activation temperature for thermal response, with water spray parameters for suppression simulation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to configure as sprinkler
rtiNoResponse Time Index in (m·s)^0.5. Default: 50
activationTemperatureNoActivation temperature in Celsius. Default: 68
flowRateNoWater flow rate in L/min. Default: 75
dropletDiameterNoMedian droplet diameter in micrometers. Default: 500
sprayAngleNoSpray angle range [min, max] in degrees. Default: [60, 75]
particlesPerSecondNoNumber of particles per second. Default: 5000
deviceIdNoCustom device ID. Default: auto-generated

Implementation Reference

  • Specific handler logic for 'bulc_set_fds_sprinkler': parses arguments using SetSprinklerSchema and sends 'set_fds_sprinkler' action to BULC client.
    case "bulc_set_fds_sprinkler": {
      const validated = SetSprinklerSchema.parse(args);
      result = await client.sendCommand({
        action: "set_fds_sprinkler",
        params: validated,
      });
      break;
    }
  • MCP tool definition including name, description, and inputSchema for 'bulc_set_fds_sprinkler'.
    {
      name: "bulc_set_fds_sprinkler",
      description:
        "Configure a furniture item as an FDS sprinkler. " +
        "Uses RTI and activation temperature for thermal response, " +
        "with water spray parameters for suppression simulation.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to configure as sprinkler",
          },
          rti: {
            type: "number",
            description: "Response Time Index in (m·s)^0.5. Default: 50",
          },
          activationTemperature: {
            type: "number",
            description: "Activation temperature in Celsius. Default: 68",
          },
          flowRate: {
            type: "number",
            description: "Water flow rate in L/min. Default: 75",
          },
          dropletDiameter: {
            type: "number",
            description: "Median droplet diameter in micrometers. Default: 500",
          },
          sprayAngle: {
            type: "array",
            description: "Spray angle range [min, max] in degrees. Default: [60, 75]",
            items: { type: "number" },
          },
          particlesPerSecond: {
            type: "integer",
            description: "Number of particles per second. Default: 5000",
          },
          deviceId: {
            type: "string",
            description: "Custom device ID. Default: auto-generated",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema for validating input parameters of 'bulc_set_fds_sprinkler' tool.
    const SetSprinklerSchema = z.object({
      furnitureId: z.string(),
      rti: z.number().positive().optional(),
      activationTemperature: z.number().optional(),
      flowRate: z.number().positive().optional(),
      dropletDiameter: z.number().positive().optional(),
      sprayAngle: z.array(z.number()).length(2).optional(),
      particlesPerSecond: z.number().int().positive().optional(),
      deviceId: z.string().optional(),
    });
  • src/index.ts:84-94 (registration)
    Routing logic in main server handler that directs calls to 'bulc_set_fds_sprinkler' to the fds-data handler.
    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);
    }
  • src/index.ts:40-45 (registration)
    Inclusion of fdsDataTools (containing 'bulc_set_fds_sprinkler') into the full list of tools served by the MCP server.
    const allTools = [
      ...contextTools,      // 8 tools: spatial context, home info, levels, undo/redo, save
      ...roomTools,         // 5 tools: create, create_polygon, list, modify, delete
      ...wallTools,         // 5 tools: create, create_rectangle, list, modify, delete
      ...furnitureTools,    // 5 tools: catalog, place, list, modify, delete
      ...fdsDataTools,      // 7 tools: get, fire_source, detector, sprinkler, hvac, thermocouple, clear
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 does not contradict. The description adds valuable context beyond annotations by specifying that it configures for 'thermal response' and 'suppression simulation', giving insight into the tool's functional behavior. However, it does not detail side effects like data overwrites or performance impacts.

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 a single, efficient sentence that front-loads the core action and key parameters without redundancy. Every word contributes to understanding the tool's function, making it appropriately sized 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 destructiveHint=true annotation and lack of output schema, the description adequately covers the basic configuration purpose but could be more complete. It does not explain what happens to existing sprinkler configurations, error conditions, or return values, which are important for a destructive operation with 8 parameters.

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 8 parameters. The description adds minimal semantics by mentioning 'RTI and activation temperature for thermal response' and 'water spray parameters for suppression simulation', which loosely maps to some parameters but does not provide additional syntax or constraints beyond the schema.

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 verb ('configure') and resource ('a furniture item as an FDS sprinkler'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'bulc_set_fds_detector' or 'bulc_set_fds_fire_source', which also configure FDS components, so it misses full sibling distinction.

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 FDS configuration tools in the sibling list. It lacks context on prerequisites, dependencies, or scenarios where this tool is appropriate, leaving the agent without 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