Skip to main content
Glama
using76
by using76

bulc_modify_wall

Destructive

Modify existing wall properties in building designs by adjusting dimensions, position, or thickness to update architectural layouts.

Instructions

Modify properties of an existing wall. Only specified properties will be changed. Get wall IDs from bulc_list_walls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWall ID to modify (from bulc_list_walls)
xStartNoNew start X (cm)
yStartNoNew start Y (cm)
xEndNoNew end X (cm)
yEndNoNew end Y (cm)
thicknessNoNew thickness (cm)
heightNoNew height (cm)

Implementation Reference

  • Specific handler case for 'bulc_modify_wall' tool: validates input with ModifyWallSchema and sends 'modify_wall' command to BULC client.
    case "bulc_modify_wall": {
      const validated = ModifyWallSchema.parse(args);
      result = await client.sendCommand({
        action: "modify_wall",
        params: validated,
      });
      break;
  • Zod schema used for runtime input validation of bulc_modify_wall parameters.
    const ModifyWallSchema = z.object({
      id: z.string(),
      xStart: z.number().optional(),
      yStart: z.number().optional(),
      xEnd: z.number().optional(),
      yEnd: z.number().optional(),
      thickness: z.number().positive().optional(),
      height: z.number().positive().optional(),
    });
  • Tool metadata registration in wallTools array, including MCP inputSchema, description, and annotations for bulc_modify_wall.
    {
      name: "bulc_modify_wall",
      description:
        "Modify properties of an existing wall. Only specified properties will be changed. " +
        "Get wall IDs from bulc_list_walls.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Wall ID to modify (from bulc_list_walls)",
          },
          xStart: { type: "number", description: "New start X (cm)" },
          yStart: { type: "number", description: "New start Y (cm)" },
          xEnd: { type: "number", description: "New end X (cm)" },
          yEnd: { type: "number", description: "New end Y (cm)" },
          thickness: { type: "number", description: "New thickness (cm)" },
          height: { type: "number", description: "New height (cm)" },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:40-51 (registration)
    Combines wallTools (including bulc_modify_wall) into allTools list advertised via 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:74-76 (registration)
    Main MCP tool call dispatcher routes bulc_*_wall tools (including bulc_modify_wall) to wall handler.
    if (name.startsWith("bulc_") && name.includes("wall")) {
      return await handleWallTool(name, safeArgs);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating this is a destructive write operation. The description adds useful context about partial updates ('Only specified properties will be changed'), which isn't captured in annotations. However, it doesn't disclose other behavioral traits like permission requirements, error conditions, or what happens to unspecified properties.

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 purpose, the second provides crucial behavioral context about partial updates and directs to the ID source tool. No wasted words, well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive modification tool with no output schema, the description provides adequate but minimal context. It covers the basic purpose and partial update behavior, but lacks information about return values, error handling, or system state changes. Given the destructive annotation and 7 parameters, more completeness would be beneficial.

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 schema already documents all 7 parameters thoroughly. The description adds minimal value by mentioning wall IDs come from 'bulc_list_walls', which is already in the schema's id description. No additional parameter semantics are provided beyond what's in the structured schema.

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 wall'), making the purpose explicit. It distinguishes from sibling 'bulc_create_wall' by specifying 'existing wall', but doesn't differentiate from other modify tools like 'bulc_modify_room' or 'bulc_modify_furniture' beyond the resource type.

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 ('Modify properties of an existing wall') and explicitly directs users to get wall IDs from 'bulc_list_walls'. However, it doesn't specify when NOT to use this tool or mention alternatives like 'bulc_delete_wall' followed by recreation.

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