Skip to main content
Glama
using76
by using76

bulc_delete_furniture

Destructive

Remove furniture items from building designs by specifying their unique ID, enabling precise editing of spatial layouts in fire simulation projects.

Instructions

Delete a furniture item by its ID. Get furniture IDs from bulc_list_furniture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFurniture ID to delete

Implementation Reference

  • Handler logic for the bulc_delete_furniture tool. Validates the input arguments using DeleteFurnitureSchema and sends a 'delete_furniture' command to the BULC client.
    case "bulc_delete_furniture": {
      const validated = DeleteFurnitureSchema.parse(args);
      result = await client.sendCommand({
        action: "delete_furniture",
        params: validated,
      });
      break;
    }
  • Zod validation schema for the input to bulc_delete_furniture, requiring a 'id' string.
    const DeleteFurnitureSchema = z.object({
      id: z.string(),
    });
  • Tool registration entry for bulc_delete_furniture in the furnitureTools export array, including name, description, input schema, and annotations.
    {
      name: "bulc_delete_furniture",
      description: "Delete a furniture item by its ID. Get furniture IDs from bulc_list_furniture.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Furniture ID to delete",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Static input schema definition embedded in the tool registration for bulc_delete_furniture.
    inputSchema: {
      type: "object" as const,
      properties: {
        id: {
          type: "string",
          description: "Furniture ID to delete",
        },
      },
      required: ["id"],
    },
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a destructive write operation. The description adds valuable context by specifying what gets destroyed ('furniture item') and how to obtain the required ID, though it doesn't mention permissions, rate limits, or confirmation requirements. With annotations covering the safety profile, this additional context warrants a score above baseline.

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 consists of two perfectly focused sentences with zero wasted words. The first sentence states the core purpose, and the second provides essential prerequisite information. Every word earns its place in this efficiently structured description.

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 operation with good annotations (readOnlyHint=false, destructiveHint=true) and complete schema coverage, the description provides adequate context. It explains what gets deleted and how to obtain the required parameter. The main gap is the lack of output schema, but the description compensates reasonably well given the tool's straightforward nature.

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 the single parameter 'id' fully documented in the schema as 'Furniture ID to delete'. The description adds marginal value by reinforcing that IDs come from bulc_list_furniture, but doesn't provide additional syntax or format details beyond what the schema already provides.

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 ('furniture item by its ID'), distinguishing it from sibling tools like bulc_modify_furniture or bulc_place_furniture. It provides a precise verb+resource combination that leaves no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/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 furniture item by its ID') and provides a clear alternative for obtaining the required parameter ('Get furniture IDs from bulc_list_furniture'). This gives the agent complete guidance on prerequisites and distinguishes it from other furniture-related operations.

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