Skip to main content
Glama
using76
by using76

bulc_create_walls_rectangle

Destructive

Create four connected walls to form a rectangular room enclosure in building design software. Specify coordinates, dimensions, and wall properties to define the room's boundaries.

Instructions

Create 4 connected walls forming a rectangular enclosure. This is the recommended way to create walls for rectangular rooms. All coordinates are in centimeters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate of bottom-left corner (cm)
yYesY coordinate of bottom-left corner (cm)
widthYesRectangle width in centimeters
depthYesRectangle depth in centimeters
thicknessNoWall thickness in centimeters. Default: 10
heightNoWall height in centimeters. Default: 250
levelNoFloor level index. Default: current level

Implementation Reference

  • Handler implementation for the 'bulc_create_walls_rectangle' tool. Validates input using Zod schema and sends 'create_walls_rectangle' action to BULC client via getBulcClient().
    case "bulc_create_walls_rectangle": {
      const validated = CreateWallsRectangleSchema.parse(args);
      result = await client.sendCommand({
        action: "create_walls_rectangle",
        params: validated,
      });
      break;
    }
  • Zod validation schema used in the handler for input parameters of bulc_create_walls_rectangle.
    const CreateWallsRectangleSchema = z.object({
      x: z.number(),
      y: z.number(),
      width: z.number().positive(),
      depth: z.number().positive(),
      thickness: z.number().positive().optional(),
      height: z.number().positive().optional(),
      level: z.number().int().optional(),
    });
  • JSON schema for input validation of bulc_create_walls_rectangle tool, provided to MCP protocol.
    inputSchema: {
      type: "object" as const,
      properties: {
        x: {
          type: "number",
          description: "X coordinate of bottom-left corner (cm)",
        },
        y: {
          type: "number",
          description: "Y coordinate of bottom-left corner (cm)",
        },
        width: {
          type: "number",
          description: "Rectangle width in centimeters",
        },
        depth: {
          type: "number",
          description: "Rectangle depth in centimeters",
        },
        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: ["x", "y", "width", "depth"],
    },
  • Tool definition and registration within the wallTools array exported for inclusion in main allTools.
    {
      name: "bulc_create_walls_rectangle",
      description:
        "Create 4 connected walls forming a rectangular enclosure. " +
        "This is the recommended way to create walls for rectangular rooms. " +
        "All coordinates are in centimeters.",
      inputSchema: {
        type: "object" as const,
        properties: {
          x: {
            type: "number",
            description: "X coordinate of bottom-left corner (cm)",
          },
          y: {
            type: "number",
            description: "Y coordinate of bottom-left corner (cm)",
          },
          width: {
            type: "number",
            description: "Rectangle width in centimeters",
          },
          depth: {
            type: "number",
            description: "Rectangle depth in centimeters",
          },
          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: ["x", "y", "width", "depth"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:73-76 (registration)
    Main tool call routing logic that directs calls to bulc_*_wall tools, including bulc_create_walls_rectangle, to the specific handleWallTool function.
    // Wall tools
    if (name.startsWith("bulc_") && name.includes("wall")) {
      return await handleWallTool(name, safeArgs);
    }
Behavior4/5

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

Annotations already indicate this is a destructive write operation (readOnlyHint: false, destructiveHint: true). The description adds valuable context by specifying that coordinates are in centimeters, which is important for correct usage. However, it doesn't mention potential side effects like overwriting existing geometry or specific permission 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 perfectly concise with two sentences that each serve distinct purposes: the first defines the tool's function and recommended use case, the second provides critical unit information. There's no wasted language or unnecessary elaboration.

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 creation tool with no output schema, the description provides adequate context about what it creates and the coordinate system. However, it doesn't describe what the tool returns (e.g., wall IDs, success confirmation) or potential error conditions, which would be helpful given the destructive nature indicated by annotations.

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, all parameters are well-documented in the schema itself. The description adds only the unit context ('All coordinates are in centimeters'), which is helpful but doesn't provide additional semantic meaning beyond what the schema already offers. 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.

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 4 connected walls forming a rectangular enclosure') and resource ('walls'), distinguishing it from siblings like 'bulc_create_wall' (single wall) and 'bulc_create_room' (room creation). It explicitly positions this as 'the recommended way to create walls for rectangular rooms,' providing clear differentiation.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('for rectangular rooms'), but doesn't explicitly state when not to use it or mention specific alternatives. While it implies rectangular scenarios, it doesn't contrast with other wall-creation methods or room-creation tools in the sibling list.

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