Skip to main content
Glama
using76
by using76

bulc_create_room_polygon

Destructive

Create custom-shaped rooms in building designs by defining polygon coordinates. Design L-shaped or irregular rooms using precise centimeter measurements for architectural planning.

Instructions

Create a room with a custom polygon shape defined by an array of points. Use this for non-rectangular rooms like L-shaped rooms. All coordinates are in centimeters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYesArray of [x, y] coordinate pairs defining the room polygon in centimeters. Minimum 3 points required. Points should be in order (clockwise or counter-clockwise).
nameNoRoom name for display
levelNoFloor level index. Default: current level

Implementation Reference

  • Handler logic for the 'bulc_create_room_polygon' tool: parses input arguments using Zod schema and sends a 'create_room_polygon' command to the BULC client.
    case "bulc_create_room_polygon": {
      const validated = CreateRoomPolygonSchema.parse(args);
      result = await client.sendCommand({
        action: "create_room_polygon",
        params: validated,
      });
      break;
    }
  • Registration of the 'bulc_create_room_polygon' tool in the roomTools array, including name, description, input schema, and annotations.
    {
      name: "bulc_create_room_polygon",
      description:
        "Create a room with a custom polygon shape defined by an array of points. " +
        "Use this for non-rectangular rooms like L-shaped rooms. " +
        "All coordinates are in centimeters.",
      inputSchema: {
        type: "object" as const,
        properties: {
          points: {
            type: "array",
            description:
              "Array of [x, y] coordinate pairs defining the room polygon in centimeters. " +
              "Minimum 3 points required. Points should be in order (clockwise or counter-clockwise).",
            items: {
              type: "array",
              items: { type: "number" },
              minItems: 2,
              maxItems: 2,
            },
            minItems: 3,
          },
          name: {
            type: "string",
            description: "Room name for display",
          },
          level: {
            type: "integer",
            description: "Floor level index. Default: current level",
          },
        },
        required: ["points"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema used in the handler for input validation of 'bulc_create_room_polygon' tool.
    const CreateRoomPolygonSchema = z.object({
      points: z.array(z.tuple([z.number(), z.number()])).min(3),
      name: z.string().optional(),
      level: z.number().int().optional(),
    });
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 doesn't contradict. The description adds valuable context beyond annotations by specifying the coordinate system ('All coordinates are in centimeters'), which is important behavioral information not captured in structured fields. It doesn't mention side effects or permissions, but with annotations covering the safety profile, this is sufficient.

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 functionality and differentiation, the second provides essential coordinate context. No wasted words, well-structured, and front-loaded with the main purpose.

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 destructive annotations and no output schema, the description provides adequate context about what it creates and the coordinate system. However, it doesn't mention what happens on success/failure or the format of any return value, which would be helpful given the absence of an output schema. Still, it's reasonably complete for the tool's complexity.

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 already documents all three parameters thoroughly. The description adds minimal parameter semantics beyond the schema (only mentioning 'coordinates are in centimeters', which is already implied in the schema's points description). This meets the baseline of 3 when 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 room') with the distinctive feature ('with a custom polygon shape defined by an array of points'), explicitly distinguishing it from sibling tools like 'bulc_create_room' (likely for rectangular rooms) by mentioning 'non-rectangular rooms like L-shaped rooms'. It provides verb+resource+scope with 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 for when to use this tool ('for non-rectangular rooms like L-shaped rooms'), which implicitly distinguishes it from rectangular room creation tools. However, it doesn't explicitly name alternatives or provide when-not-to-use guidance, keeping it at a 4 rather than a perfect 5.

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