Skip to main content
Glama
using76
by using76

bulc_create_wall

Destructive

Create custom wall segments in building designs by specifying start and end coordinates, thickness, and height for precise spatial layout in fire simulation software.

Instructions

Create a wall segment between two points. All coordinates are in centimeters. For rectangular rooms, consider using bulc_create_walls_rectangle instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xStartYesX coordinate of wall start point (cm)
yStartYesY coordinate of wall start point (cm)
xEndYesX coordinate of wall end point (cm)
yEndYesY coordinate of wall end point (cm)
thicknessNoWall thickness in centimeters. Default: 10
heightNoWall height in centimeters. Default: 250
levelNoFloor level index. Default: current level

Implementation Reference

  • Handler logic for 'bulc_create_wall': parses arguments with Zod schema and sends 'create_wall' command to BULC client.
    case "bulc_create_wall": {
      const validated = CreateWallSchema.parse(args);
      result = await client.sendCommand({
        action: "create_wall",
        params: validated,
      });
      break;
    }
  • Tool definition including name, description, and input schema for MCP tool registration.
    {
      name: "bulc_create_wall",
      description:
        "Create a wall segment between two points. " +
        "All coordinates are in centimeters. " +
        "For rectangular rooms, consider using bulc_create_walls_rectangle instead.",
      inputSchema: {
        type: "object" as const,
        properties: {
          xStart: {
            type: "number",
            description: "X coordinate of wall start point (cm)",
          },
          yStart: {
            type: "number",
            description: "Y coordinate of wall start point (cm)",
          },
          xEnd: {
            type: "number",
            description: "X coordinate of wall end point (cm)",
          },
          yEnd: {
            type: "number",
            description: "Y coordinate of wall end point (cm)",
          },
          thickness: {
            type: "number",
            description: "Wall thickness in centimeters. Default: 10",
          },
          height: {
            type: "number",
            description: "Wall height in centimeters. Default: 250",
          },
          level: {
            type: "integer",
            description: "Floor level index. Default: current level",
          },
        },
        required: ["xStart", "yStart", "xEnd", "yEnd"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema for input parameters of bulc_create_wall.
    const CreateWallSchema = z.object({
      xStart: z.number(),
      yStart: z.number(),
      xEnd: z.number(),
      yEnd: z.number(),
      thickness: z.number().positive().optional(),
      height: z.number().positive().optional(),
      level: z.number().int().optional(),
    });
  • src/index.ts:40-51 (registration)
    Includes wallTools (containing bulc_create_wall) in the complete list of tools registered with 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
      ...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:73-75 (registration)
    Routes tool calls matching 'bulc_*wall*' to the handleWallTool function.
    // Wall tools
    if (name.startsWith("bulc_") && name.includes("wall")) {
      return await handleWallTool(name, safeArgs);
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating this is a destructive write operation. The description adds useful context about coordinate units (centimeters) but doesn't provide additional behavioral details like what 'destructive' means in practice (e.g., overwrites existing walls, requires specific permissions, or has irreversible effects). With annotations covering the basic safety profile, the description adds some value but not rich behavioral context.

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 that each earn their place: the first states the core purpose with essential unit information, and the second provides crucial sibling tool guidance. No wasted words, well-structured, and front-loaded.

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 creation tool with good annotations (destructiveHint=true) and comprehensive schema coverage, the description provides adequate context. It covers purpose, units, and sibling differentiation. The main gap is lack of output information (no output schema exists), but for a wall creation operation, the description is reasonably complete given the structured data available.

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 all parameters are well-documented in the input schema. The description adds the coordinate unit context ('All coordinates are in centimeters') which is helpful, but doesn't provide additional parameter semantics beyond what the schema already specifies. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Create a wall segment') and resource ('between two points'), with explicit coordinate units ('in centimeters'). It distinguishes from sibling 'bulc_create_walls_rectangle' by indicating this tool is for general wall segments while the alternative is for rectangular rooms.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use an alternative tool: 'For rectangular rooms, consider using bulc_create_walls_rectangle instead.' This directly addresses sibling tool differentiation and gives clear context for tool selection.

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