Skip to main content
Glama
using76
by using76

bulc_clear_fds_data

Destructive

Remove fire safety simulation data from furniture items, including fire sources, detectors, sprinklers, HVAC, and thermocouple configurations.

Instructions

Clear FDS configuration from a furniture item. Removes fire source, detector, sprinkler, HVAC, or thermocouple settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to clear FDS data from

Implementation Reference

  • Handler logic for the 'bulc_clear_fds_data' tool. Validates the input arguments using ClearFdsDataSchema and sends a 'clear_fds_data' command to the BULC client.
    case "bulc_clear_fds_data": {
      const validated = ClearFdsDataSchema.parse(args);
      result = await client.sendCommand({
        action: "clear_fds_data",
        params: validated,
      });
      break;
    }
  • Tool schema definition for 'bulc_clear_fds_data', including name, description, input schema requiring 'furnitureId', and annotations indicating it's destructive.
    {
      name: "bulc_clear_fds_data",
      description:
        "Clear FDS configuration from a furniture item. " +
        "Removes fire source, detector, sprinkler, HVAC, or thermocouple settings.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to clear FDS data from",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema for the input of 'bulc_clear_fds_data' tool, ensuring 'furnitureId' is a string.
    const ClearFdsDataSchema = z.object({
      furnitureId: z.string(),
    });
  • src/index.ts:84-93 (registration)
    Registration/routing in the main tool call handler: routes 'bulc_clear_fds_data' (and other FDS tools) to handleFdsDataTool.
    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-51 (registration)
    Includes fdsDataTools (containing 'bulc_clear_fds_data' schema) in the allTools array returned by listTools handler.
    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
      ...meshTools,         // 5 tools: list, create, auto, modify, delete
      ...simulationTools,   // 4 tools: get_settings, time, output, ambient
      ...fdsRunTools,       // 6 tools: preview, validate, export, run, status, stop
      ...resultTools,       // 5 tools: open_viewer, list_datasets, point_data, aset, report
      ...evacTools,         // 25 tools: setup, stairs, agents, run, results, advanced features
    ];
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 using 'Clear' and 'Removes'. The description adds valuable context beyond annotations by specifying exactly what types of FDS settings get removed (fire source, detector, sprinkler, HVAC, thermocouple), which helps the agent understand the scope of the destructive operation.

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 perfectly concise with two sentences: the first states the core purpose, and the second provides specific examples of what gets cleared. Every word earns its place, and the structure is front-loaded with the main action.

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?

For a destructive operation with good annotations and a simple single parameter, the description provides adequate context. It specifies what gets cleared, aligns with annotations, and distinguishes from read/set operations. The main gap is lack of output information (no output schema), but the description compensates reasonably given the tool's straightforward nature.

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% with the single parameter 'furnitureId' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, but with complete schema coverage, the baseline score of 3 is appropriate as the schema carries the full burden.

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 ('Clear FDS configuration') and target ('from a furniture item'), with specific examples of what gets removed (fire source, detector, sprinkler, HVAC, thermocouple settings). It distinguishes from siblings like 'bulc_get_fds_data' (read) and 'bulc_set_fds_*' tools (configure), but doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

The description implies usage when FDS configuration needs to be removed from furniture, suggesting it's for resetting or clearing settings. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'bulc_delete_furniture' or 'bulc_modify_furniture', nor does it mention prerequisites or exclusions.

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