Skip to main content
Glama
using76
by using76

bulc_setup_evac_stair

Destructive

Configure furniture as evacuation stairs between floors to define entry/exit points, capacity, and travel speed for building safety simulations.

Instructions

Configure a furniture item as an evacuation stair connection between floors. Defines entry/exit positions, capacity, and travel speed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to configure as stair
fromFloorYesSource floor index (0=ground floor)
toFloorYesDestination floor index
entryXNoEntry point X coordinate in cm
entryYNoEntry point Y coordinate in cm
exitXNoExit point X coordinate in cm
exitYNoExit point Y coordinate in cm
widthNoStair width in meters. Default: 1.2
capacityNoMax people on stair at once. Default: 10
travelSpeedNoTravel speed in m/s. Default: 0.6

Implementation Reference

  • Specific handler case for 'bulc_setup_evac_stair' tool within the main handleEvacTool function. Validates input parameters using SetupEvacStairSchema and forwards the command to the BULC client backend.
    case "bulc_setup_evac_stair": {
      const validated = SetupEvacStairSchema.parse(args);
      result = await client.sendCommand({
        action: "setup_evac_stair",
        params: validated,
      });
      break;
  • MCP tool schema definition including name, description, detailed input schema, and annotations. Part of the evacTools array.
    {
      name: "bulc_setup_evac_stair",
      description:
        "Configure a furniture item as an evacuation stair connection between floors. " +
        "Defines entry/exit positions, capacity, and travel speed.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to configure as stair",
          },
          fromFloor: {
            type: "integer",
            description: "Source floor index (0=ground floor)",
          },
          toFloor: {
            type: "integer",
            description: "Destination floor index",
          },
          entryX: {
            type: "number",
            description: "Entry point X coordinate in cm",
          },
          entryY: {
            type: "number",
            description: "Entry point Y coordinate in cm",
          },
          exitX: {
            type: "number",
            description: "Exit point X coordinate in cm",
          },
          exitY: {
            type: "number",
            description: "Exit point Y coordinate in cm",
          },
          width: {
            type: "number",
            description: "Stair width in meters. Default: 1.2",
          },
          capacity: {
            type: "integer",
            description: "Max people on stair at once. Default: 10",
          },
          travelSpeed: {
            type: "number",
            description: "Travel speed in m/s. Default: 0.6",
          },
        },
        required: ["furnitureId", "fromFloor", "toFloor"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod runtime validation schema matching the MCP inputSchema, used in the handler for safe parameter parsing.
    const SetupEvacStairSchema = z.object({
      furnitureId: z.string(),
      fromFloor: z.number().int().min(0),
      toFloor: z.number().int().min(0),
      entryX: z.number().optional(),
      entryY: z.number().optional(),
      exitX: z.number().optional(),
      exitY: z.number().optional(),
      width: z.number().positive().optional(),
      capacity: z.number().int().positive().optional(),
      travelSpeed: z.number().positive().optional(),
    });
  • src/index.ts:40-51 (registration)
    Registration of all tool schemas including evacTools (containing bulc_setup_evac_stair) into the combined allTools array, provided to MCP ListToolsRequest.
    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
    ];
  • src/index.ts:135-137 (registration)
    Routing logic in main MCP CallToolRequest handler that directs 'bulc_setup_evac_stair' (matches 'evac') calls to the evac-specific handleEvacTool dispatcher.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(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 by specifying what gets configured (entry/exit positions, capacity, travel speed) and the resource type (furniture item as stair connection), though it doesn't detail side effects like overwriting existing stair settings or validation requirements.

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 ('Configure a furniture item as an evacuation stair connection') and follows with key configuration aspects. Every word contributes to understanding the tool's purpose without redundancy or unnecessary detail.

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 10 parameters and no output schema, the description is adequate but incomplete. It covers the basic purpose and configuration scope, but lacks details on behavioral outcomes (e.g., what happens if the furnitureId is invalid), error conditions, or return values, which are important given the tool's complexity and destructive 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?

With 100% schema description coverage, the input schema fully documents all 10 parameters. The description adds minimal semantics by mentioning 'entry/exit positions, capacity, and travel speed', which loosely maps to parameters like entryX/Y, exitX/Y, capacity, and travelSpeed, but doesn't provide additional meaning or usage context beyond what the schema already specifies.

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 evacuation stair connection') and resource ('between floors'), distinguishing it from siblings like 'bulc_clear_evac_stair' (which removes stairs) and 'bulc_modify_evac_stair' (which modifies existing stairs). It explicitly defines the configuration scope with 'entry/exit positions, capacity, and travel speed'.

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 like 'bulc_modify_evac_stair' or 'bulc_clear_evac_stair', nor does it mention prerequisites such as needing an existing furniture item or valid floor indices. It lacks context about whether this is for initial setup or replacement.

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