Skip to main content
Glama
using76
by using76

bulc_modify_evac_stair

Destructive

Modify evacuation stair properties like capacity, speed, and position to optimize building safety and compliance in fire simulations.

Instructions

Modify an existing evacuation stair configuration. Update capacity, speed, or position properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID of the stair to modify
entryXNoNew entry point X coordinate in cm
entryYNoNew entry point Y coordinate in cm
exitXNoNew exit point X coordinate in cm
exitYNoNew exit point Y coordinate in cm
widthNoNew stair width in meters
capacityNoNew maximum capacity
travelSpeedNoNew travel speed in m/s

Implementation Reference

  • Tool registration in evacTools array, defining name, description, input schema, and annotations for MCP tool listing.
    {
      name: "bulc_modify_evac_stair",
      description:
        "Modify an existing evacuation stair configuration. " +
        "Update capacity, speed, or position properties.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID of the stair to modify",
          },
          entryX: {
            type: "number",
            description: "New entry point X coordinate in cm",
          },
          entryY: {
            type: "number",
            description: "New entry point Y coordinate in cm",
          },
          exitX: {
            type: "number",
            description: "New exit point X coordinate in cm",
          },
          exitY: {
            type: "number",
            description: "New exit point Y coordinate in cm",
          },
          width: {
            type: "number",
            description: "New stair width in meters",
          },
          capacity: {
            type: "integer",
            description: "New maximum capacity",
          },
          travelSpeed: {
            type: "number",
            description: "New travel speed in m/s",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema used for runtime input validation in the tool handler.
    const ModifyEvacStairSchema = z.object({
      furnitureId: z.string(),
      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(),
    });
  • Handler logic within handleEvacTool switch statement: validates input and sends 'modify_evac_stair' action to BULC client.
    case "bulc_modify_evac_stair": {
      const validated = ModifyEvacStairSchema.parse(args);
      result = await client.sendCommand({
        action: "modify_evac_stair",
        params: validated,
      });
      break;
    }
  • src/index.ts:40-51 (registration)
    MCP tool list registration: evacTools spread into allTools, returned by ListToolsRequestHandler.
    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
    ];
  • Main MCP CallToolRequestHandler routing: dispatches 'bulc_*evac*' tools to handleEvacTool.
    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 using 'Modify' and 'Update'. The description adds value by specifying which properties can be modified (capacity, speed, position), which isn't covered by annotations. However, it doesn't disclose potential side effects (e.g., impact on evacuation simulations) or error conditions, leaving some behavioral gaps.

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 ('Modify an existing evacuation stair configuration') and lists key updatable properties. There is no wasted text, and it's appropriately sized for the tool's complexity.

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 destructiveHint=true, no output schema, and 8 parameters, the description is minimally adequate. It covers the purpose and key properties but lacks details on behavioral implications (e.g., how modifications affect simulations), error handling, or return values. With annotations providing safety context, it's complete enough for basic use but could be more informative.

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 the schema fully documents all 8 parameters. The description mentions 'capacity, speed, or position properties', which loosely maps to parameters like capacity, travelSpeed, and entry/exit coordinates, but adds no syntax, units, or constraints beyond the schema. This meets the baseline for high schema 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 ('Modify') and resource ('existing evacuation stair configuration'), and specifies the properties that can be updated ('capacity, speed, or position'). It distinguishes from siblings like 'bulc_setup_evac_stair' (creation) and 'bulc_clear_evac_stair' (deletion), though it doesn't explicitly name them. However, it could be more specific about what 'position properties' entails.

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. It doesn't mention prerequisites (e.g., an existing stair must be identified by furnitureId), exclusions, or comparisons to siblings like 'bulc_modify_furniture' or 'bulc_setup_evac_stair'. Usage is implied by the verb 'Modify' but lacks explicit context.

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