Skip to main content
Glama
using76
by using76

bulc_place_furniture

Destructive

Place furniture items in building designs using catalog IDs and precise centimeter coordinates, with options for custom dimensions, rotation, and floor level placement.

Instructions

Place a furniture item at the specified position. Get catalog IDs from bulc_list_furniture_catalog first. All coordinates are in centimeters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalogIdYesCatalog ID from bulc_list_furniture_catalog
xYesX coordinate in centimeters
yYesY coordinate in centimeters
elevationNoHeight from floor in centimeters. Default: 0
angleNoRotation angle in degrees (0-360). Default: 0
widthNoCustom width in centimeters (optional, overrides catalog)
depthNoCustom depth in centimeters (optional, overrides catalog)
heightNoCustom height in centimeters (optional, overrides catalog)
nameNoCustom name for display
levelNoFloor level index. Default: current level

Implementation Reference

  • Handler logic for 'bulc_place_furniture': parses arguments using PlaceFurnitureSchema and sends a 'place_furniture' command to the BULC client.
    case "bulc_place_furniture": {
      const validated = PlaceFurnitureSchema.parse(args);
      result = await client.sendCommand({
        action: "place_furniture",
        params: validated,
      });
      break;
    }
  • Tool schema definition for 'bulc_place_furniture' including name, description, inputSchema, and annotations, exported as part of furnitureTools array.
    {
      name: "bulc_place_furniture",
      description:
        "Place a furniture item at the specified position. " +
        "Get catalog IDs from bulc_list_furniture_catalog first. " +
        "All coordinates are in centimeters.",
      inputSchema: {
        type: "object" as const,
        properties: {
          catalogId: {
            type: "string",
            description: "Catalog ID from bulc_list_furniture_catalog",
          },
          x: {
            type: "number",
            description: "X coordinate in centimeters",
          },
          y: {
            type: "number",
            description: "Y coordinate in centimeters",
          },
          elevation: {
            type: "number",
            description: "Height from floor in centimeters. Default: 0",
          },
          angle: {
            type: "number",
            description: "Rotation angle in degrees (0-360). Default: 0",
          },
          width: {
            type: "number",
            description: "Custom width in centimeters (optional, overrides catalog)",
          },
          depth: {
            type: "number",
            description: "Custom depth in centimeters (optional, overrides catalog)",
          },
          height: {
            type: "number",
            description: "Custom height in centimeters (optional, overrides catalog)",
          },
          name: {
            type: "string",
            description: "Custom name for display",
          },
          level: {
            type: "integer",
            description: "Floor level index. Default: current level",
          },
        },
        required: ["catalogId", "x", "y"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema (PlaceFurnitureSchema) for inputs to the bulc_place_furniture tool.
    const PlaceFurnitureSchema = z.object({
      catalogId: z.string(),
      x: z.number(),
      y: z.number(),
      elevation: z.number().optional(),
      angle: z.number().optional(),
      width: z.number().positive().optional(),
      depth: z.number().positive().optional(),
      height: z.number().positive().optional(),
      name: z.string().optional(),
      level: z.number().int().optional(),
    });
  • src/index.ts:40-51 (registration)
    Registration of tool schemas: spreads furnitureTools (including bulc_place_furniture) into the 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:79-81 (registration)
    Handler routing registration: dispatches calls to 'bulc_place_furniture' (and other furniture tools) to handleFurnitureTool.
    if (name.startsWith("bulc_") && name.includes("furniture")) {
      return await handleFurnitureTool(name, safeArgs);
    }
Behavior4/5

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

The annotations indicate readOnlyHint=false and destructiveHint=true, which the description aligns with by implying a write operation ('Place'). The description adds valuable context beyond annotations by specifying the coordinate system ('All coordinates are in centimeters'), which is crucial for correct usage. It doesn't detail side effects like what happens if placement fails or if furniture overlaps, but with annotations covering the destructive nature, 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 extremely concise and front-loaded, consisting of just two sentences that directly state the tool's purpose and a key usage guideline. Every word earns its place, with no redundancy or unnecessary elaboration, making it highly efficient for an AI agent.

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?

Given the tool's complexity (10 parameters, destructive operation) and lack of an output schema, the description is reasonably complete. It covers the core action, prerequisite, and coordinate system, but could benefit from mentioning potential constraints (e.g., valid coordinate ranges) or error cases. With annotations providing safety context, it's largely adequate.

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?

The input schema has 100% description coverage, with each parameter well-documented (e.g., 'Catalog ID from bulc_list_furniture_catalog' for catalogId). The description adds minimal value beyond this, only reiterating the coordinate units ('in centimeters') which is already in the schema for x, y, and elevation. Thus, it meets the baseline of 3 without significantly enhancing parameter understanding.

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 ('Place a furniture item') and the target resource ('at the specified position'), distinguishing it from sibling tools like bulc_list_furniture_catalog (which provides catalog IDs) and bulc_modify_furniture (which likely edits existing furniture). The verb 'Place' is precise and indicates creation/positioning.

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 usage by instructing to 'Get catalog IDs from bulc_list_furniture_catalog first,' which is a helpful prerequisite. However, it doesn't explicitly state when NOT to use this tool (e.g., vs. bulc_modify_furniture for editing existing items) or mention alternatives, keeping it from a perfect score.

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