Skip to main content
Glama
using76
by using76

bulc_modify_furniture

Destructive

Adjust furniture properties like position, dimensions, rotation, and visibility in building designs. Update specific attributes without recreating items.

Instructions

Modify properties of an existing furniture item. Only specified properties will be changed. Get furniture IDs from bulc_list_furniture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFurniture ID to modify (from bulc_list_furniture)
xNoNew X coordinate (cm)
yNoNew Y coordinate (cm)
elevationNoNew elevation from floor (cm)
angleNoNew rotation angle (degrees)
widthNoNew width (cm)
depthNoNew depth (cm)
heightNoNew height (cm)
nameNoNew display name
visibleNoVisibility state

Implementation Reference

  • Executes the bulc_modify_furniture tool: validates input parameters using Zod schema and sends a 'modify_furniture' command with validated params to the BULC client.
    case "bulc_modify_furniture": {
      const validated = ModifyFurnitureSchema.parse(args);
      result = await client.sendCommand({
        action: "modify_furniture",
        params: validated,
      });
      break;
    }
  • Zod input validation schema for the bulc_modify_furniture tool parameters.
    const ModifyFurnitureSchema = z.object({
      id: z.string(),
      x: z.number().optional(),
      y: z.number().optional(),
      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(),
      visible: z.boolean().optional(),
    });
  • MCP tool specification for bulc_modify_furniture: defines name, description, input schema, required fields, and annotations for tool listing.
    {
      name: "bulc_modify_furniture",
      description:
        "Modify properties of an existing furniture item. " +
        "Only specified properties will be changed. " +
        "Get furniture IDs from bulc_list_furniture.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Furniture ID to modify (from bulc_list_furniture)",
          },
          x: {
            type: "number",
            description: "New X coordinate (cm)",
          },
          y: {
            type: "number",
            description: "New Y coordinate (cm)",
          },
          elevation: {
            type: "number",
            description: "New elevation from floor (cm)",
          },
          angle: {
            type: "number",
            description: "New rotation angle (degrees)",
          },
          width: {
            type: "number",
            description: "New width (cm)",
          },
          depth: {
            type: "number",
            description: "New depth (cm)",
          },
          height: {
            type: "number",
            description: "New height (cm)",
          },
          name: {
            type: "string",
            description: "New display name",
          },
          visible: {
            type: "boolean",
            description: "Visibility state",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Dispatch routing in the MCP server's CallToolRequestHandler that routes bulc_modify_furniture calls to the furniture-specific handler.
    // Furniture tools
    if (name.startsWith("bulc_") && name.includes("furniture")) {
      return await handleFurnitureTool(name, safeArgs);
    }
  • src/index.ts:54-58 (registration)
    MCP server handler for ListToolsRequest that returns allTools array, which includes the bulc_modify_furniture specification via furnitureTools spread.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
Behavior3/5

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

Annotations indicate 'readOnlyHint: false' and 'destructiveHint: true', which already convey that this is a mutable, potentially destructive operation. The description adds value by specifying 'Only specified properties will be changed', clarifying partial updates, but doesn't disclose additional behavioral traits like error handling, permissions, or side effects beyond what annotations provide.

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 two sentences, front-loaded with the core action ('Modify properties of an existing furniture item'), followed by essential guidance. Every sentence earns its place by providing key information without redundancy, making it highly efficient and well-structured.

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 mutation) and lack of output schema, the description is reasonably complete. It covers the purpose, partial update behavior, and ID sourcing, but could benefit from mentioning response format or error cases. Annotations provide safety context, so the description doesn't need to repeat that.

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%, with each parameter clearly documented in the input schema (e.g., 'id' as 'Furniture ID to modify', 'x' as 'New X coordinate (cm)'). The description doesn't add extra meaning beyond this, as it only references the 'id' parameter indirectly. Baseline 3 is appropriate since the schema handles parameter documentation effectively.

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 verb ('Modify') and resource ('properties of an existing furniture item'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'bulc_delete_furniture' or 'bulc_place_furniture', which would require mentioning it's for updates rather than creation or deletion.

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 by stating 'Only specified properties will be changed' and directing users to 'Get furniture IDs from bulc_list_furniture', which helps in understanding when to use this tool. It doesn't explicitly mention alternatives like 'bulc_place_furniture' for new items, but the guidance is sufficient for basic usage.

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