Skip to main content
Glama
using76
by using76

bulc_delete_wall

Destructive

Remove walls from building designs by specifying their unique ID, enabling precise editing of architectural layouts within the BULC Building Designer environment.

Instructions

Delete a wall by its ID. Get wall IDs from bulc_list_walls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWall ID to delete

Implementation Reference

  • Handler case for 'bulc_delete_wall' tool: parses input with DeleteWallSchema and sends 'delete_wall' command to BULC client via getBulcClient().
    case "bulc_delete_wall": {
      const validated = DeleteWallSchema.parse(args);
      result = await client.sendCommand({
        action: "delete_wall",
        params: validated,
      });
      break;
    }
  • Tool definition including name, description, inputSchema (requiring 'id' string), and annotations for the bulc_delete_wall tool, part of exported wallTools array.
    {
      name: "bulc_delete_wall",
      description: "Delete a wall by its ID. Get wall IDs from bulc_list_walls.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Wall ID to delete",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema for validating input arguments to bulc_delete_wall handler.
    const DeleteWallSchema = z.object({
      id: z.string(),
    });
  • src/index.ts:73-76 (registration)
    Dispatch logic in main MCP server handler that routes calls to 'bulc_delete_wall' (and other wall tools) to handleWallTool.
    // Wall tools
    if (name.startsWith("bulc_") && name.includes("wall")) {
      return await handleWallTool(name, safeArgs);
    }
  • src/index.ts:43-43 (registration)
    Inclusion of wallTools (containing bulc_delete_wall) into the allTools array provided to MCP ListToolsRequest.
    ...wallTools,         // 5 tools: create, create_rectangle, list, modify, delete
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 aligns with by stating 'Delete'. The description adds valuable context by specifying that wall IDs can be obtained from 'bulc_list_walls', which is not covered by annotations. It does not detail side effects like confirmation prompts or error handling, but with annotations providing safety cues, this is acceptable.

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 with two sentences that are front-loaded and waste no words. Every sentence serves a clear purpose: the first states the action, and the second provides essential usage guidance, making it highly efficient.

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 tool with one parameter and no output schema, the description is mostly complete. It covers the action, parameter source, and aligns with annotations. However, it lacks details on potential side effects or error conditions, which could be useful given the destructive nature, though annotations mitigate this gap.

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 the 'id' parameter documented as 'Wall ID to delete'. The description adds minimal semantics by referencing 'bulc_list_walls' for obtaining IDs, but does not provide additional details like format or constraints beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 ('Delete') and resource ('a wall by its ID'), distinguishing it from siblings like 'bulc_modify_wall' or 'bulc_create_wall'. It provides a direct reference to where to obtain the required parameter ('Get wall IDs from bulc_list_walls'), which enhances clarity and 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 explicitly states when to use this tool ('Delete a wall by its ID') and provides a prerequisite ('Get wall IDs from bulc_list_walls'), which implies usage context. However, it does not specify when not to use it or name alternatives explicitly, such as 'bulc_modify_wall' for updates instead of deletion.

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