Skip to main content
Glama
using76
by using76

bulc_modify_room

Destructive

Modify existing room properties like name, position, and dimensions in BULC Building Designer. Update specific attributes without recreating rooms.

Instructions

Modify properties of an existing room. Only specified properties will be changed. Get room IDs from bulc_list_rooms first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRoom ID to modify (from bulc_list_rooms)
nameNoNew room name
xNoNew X coordinate of bottom-left corner (cm)
yNoNew Y coordinate of bottom-left corner (cm)
widthNoNew width (cm)
depthNoNew depth (cm)

Implementation Reference

  • Executes the bulc_modify_room tool by parsing arguments with ModifyRoomSchema and sending a 'modify_room' command to the BULC client.
    case "bulc_modify_room": {
      const validated = ModifyRoomSchema.parse(args);
      result = await client.sendCommand({
        action: "modify_room",
        params: validated,
      });
      break;
    }
  • Zod validation schema for the inputs to the bulc_modify_room tool.
    const ModifyRoomSchema = z.object({
      id: z.string(),
      name: z.string().optional(),
      x: z.number().optional(),
      y: z.number().optional(),
      width: z.number().positive().optional(),
      depth: z.number().positive().optional(),
    });
  • MCP tool schema definition for bulc_modify_room, including input schema, description, and annotations.
    {
      name: "bulc_modify_room",
      description:
        "Modify properties of an existing room. Only specified properties will be changed. " +
        "Get room IDs from bulc_list_rooms first.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Room ID to modify (from bulc_list_rooms)",
          },
          name: {
            type: "string",
            description: "New room name",
          },
          x: {
            type: "number",
            description: "New X coordinate of bottom-left corner (cm)",
          },
          y: {
            type: "number",
            description: "New Y coordinate of bottom-left corner (cm)",
          },
          width: {
            type: "number",
            description: "New width (cm)",
          },
          depth: {
            type: "number",
            description: "New depth (cm)",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:54-58 (registration)
    Registers all tools, including bulc_modify_room via roomTools inclusion in allTools, for the MCP ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • Dispatches calls to bulc_modify_room (and other room tools) to the handleRoomTool function.
    // Room tools
    if (name.startsWith("bulc_") && name.includes("room")) {
      return await handleRoomTool(name, safeArgs);
    }
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=true, indicating this is a mutation that may cause destructive changes. The description adds valuable context by specifying 'Only specified properties will be changed' (partial update behavior) and the prerequisite to get IDs from another tool. This goes beyond what annotations alone convey about the tool's operational characteristics.

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?

Two sentences with zero waste. The first sentence states the core purpose, the second provides essential usage guidance. Every word earns its place, and information is appropriately 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 destructive mutation tool with no output schema, the description provides good context about partial updates and ID sourcing. It could be more complete by mentioning potential side effects or what happens to unspecified properties, but given the annotations cover destructive nature and schema covers parameters well, this is reasonably complete.

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 minimal value beyond the schema by mentioning room IDs come from bulc_list_rooms (implied in the schema's id description) and that only specified properties change (partial update). 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Modify properties') and resource ('existing room'), distinguishing it from creation/deletion tools. However, it doesn't explicitly differentiate from other 'modify' siblings like bulc_modify_furniture or bulc_modify_wall, which would require a 5.

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 room IDs from bulc_list_rooms first.' This gives practical guidance on prerequisites and partial update behavior. However, it doesn't explicitly mention when NOT to use this tool or name specific alternatives among siblings.

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