Skip to main content
Glama
using76
by using76

bulc_delete_mesh

Destructive

Remove an FDS mesh from a building design simulation by specifying its ID to clean up model geometry and optimize computational resources.

Instructions

Delete an FDS mesh by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meshIdYesMesh ID to delete

Implementation Reference

  • Handler logic for the 'bulc_delete_mesh' tool: parses arguments using DeleteMeshSchema and sends a 'delete_mesh' command with validated parameters to the BULC client.
    case "bulc_delete_mesh": {
      const validated = DeleteMeshSchema.parse(args);
      result = await client.sendCommand({
        action: "delete_mesh",
        params: validated,
      });
      break;
    }
  • Tool schema definition for 'bulc_delete_mesh', including name, description, input schema requiring 'meshId', and annotations indicating it's destructive.
    {
      name: "bulc_delete_mesh",
      description: "Delete an FDS mesh by its ID.",
      inputSchema: {
        type: "object" as const,
        properties: {
          meshId: {
            type: "string",
            description: "Mesh ID to delete",
          },
        },
        required: ["meshId"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema used for input validation in the bulc_delete_mesh handler.
    const DeleteMeshSchema = z.object({
      meshId: z.string(),
    });
  • src/index.ts:40-51 (registration)
    Registration of meshTools (including bulc_delete_mesh) into the complete allTools list provided to the MCP server for tool discovery.
    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:96-99 (registration)
    Routing registration: dispatches calls to 'bulc_*_mesh' tools (including bulc_delete_mesh) to the handleMeshTool function.
    // Mesh tools
    if (name.startsWith("bulc_") && name.includes("mesh")) {
      return await handleMeshTool(name, safeArgs);
    }
Behavior3/5

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

Annotations indicate this is a destructive, non-read-only operation, which the description aligns with by using 'Delete.' However, the description adds minimal behavioral context beyond this—it doesn't specify irreversible effects, permissions required, or error conditions. With annotations covering the safety profile, a baseline 3 is appropriate as the description adds some value but lacks rich behavioral details.

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 a single, direct sentence with no wasted words, efficiently conveying the core action and parameter. It's appropriately sized for a simple tool and front-loaded with essential information.

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?

Given the tool's destructive nature (annotations hint at this), lack of output schema, and simple single parameter, the description is minimally adequate. It covers the basic action but omits important context like what happens post-deletion, error handling, or dependencies on other tools, leaving gaps in completeness.

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, clearly documenting the single 'meshId' parameter. The description mentions 'by its ID,' which reinforces the parameter's purpose but doesn't add significant semantic details beyond what the schema provides, such as format examples or constraints.

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 ('Delete') and target resource ('an FDS mesh by its ID'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'bulc_delete_room' or 'bulc_delete_wall' beyond specifying the resource type, which prevents a perfect score.

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

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a mesh ID from 'bulc_list_meshes'), exclusions, or comparisons to other deletion tools in the sibling list, leaving the agent without contextual usage cues.

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