Skip to main content
Glama
using76
by using76

bulc_auto_mesh

Destructive

Generate FDS simulation meshes from building geometry with specified resolution for rooms, walls, and multi-level structures.

Instructions

Automatically generate FDS mesh based on building geometry. Creates optimized mesh covering all rooms and walls with specified resolution. Can create single mesh or multiple meshes for multi-level buildings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cellSizeNoTarget cell size in meters. Default: 0.2 (20cm)
paddingNoPadding around geometry in meters. Default: 0.5
heightAboveRoofNoAdditional height above highest point in meters. Default: 1.0
multiMeshNoCreate separate meshes per floor level. Default: false (single mesh)
maxCellsNoMaximum total cell count. Auto-adjusts cell size if exceeded. Default: 1000000

Implementation Reference

  • Handler case for 'bulc_auto_mesh' tool: parses arguments with AutoMeshSchema and sends 'auto_mesh' action to BULC client.
    case "bulc_auto_mesh": {
      const validated = AutoMeshSchema.parse(args);
      result = await client.sendCommand({
        action: "auto_mesh",
        params: validated,
      });
      break;
    }
  • Zod schema for validating inputs to the bulc_auto_mesh tool.
    const AutoMeshSchema = z.object({
      cellSize: z.number().positive().optional(),
      padding: z.number().optional(),
      heightAboveRoof: z.number().optional(),
      multiMesh: z.boolean().optional(),
      maxCells: z.number().int().positive().optional(),
    });
  • Registration of the 'bulc_auto_mesh' tool in the meshTools array, including description, input schema, and annotations.
    {
      name: "bulc_auto_mesh",
      description:
        "Automatically generate FDS mesh based on building geometry. " +
        "Creates optimized mesh covering all rooms and walls with specified resolution. " +
        "Can create single mesh or multiple meshes for multi-level buildings.",
      inputSchema: {
        type: "object" as const,
        properties: {
          cellSize: {
            type: "number",
            description: "Target cell size in meters. Default: 0.2 (20cm)",
          },
          padding: {
            type: "number",
            description: "Padding around geometry in meters. Default: 0.5",
          },
          heightAboveRoof: {
            type: "number",
            description: "Additional height above highest point in meters. Default: 1.0",
          },
          multiMesh: {
            type: "boolean",
            description: "Create separate meshes per floor level. Default: false (single mesh)",
          },
          maxCells: {
            type: "integer",
            description: "Maximum total cell count. Auto-adjusts cell size if exceeded. Default: 1000000",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=true, indicating it's a mutation tool that destroys data. The description adds valuable context beyond annotations by specifying that it 'creates optimized mesh covering all rooms and walls' and can handle multi-level buildings, which clarifies scope and behavior. It doesn't contradict annotations, as 'creates' aligns with destructiveHint=true for mesh generation.

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 highly concise and well-structured in two sentences, with zero wasted words. The first sentence states the core purpose, and the second adds key behavioral details (optimization, room/wall coverage, single/multi-mesh options). Every sentence earns its place by providing essential information without redundancy.

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?

Given the tool's complexity (mesh generation with 5 parameters) and annotations covering mutation/destructive behavior, the description is mostly complete. It explains what the tool does and its scope but lacks details on output (no output schema) and error handling. For a destructive tool with no output schema, it could benefit from mentioning result format or success indicators, but it's adequate for basic understanding.

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 all 5 parameters well-documented in the input schema. The description adds minimal semantic value beyond the schema, mentioning 'specified resolution' which loosely relates to cellSize and 'multi-level buildings' hinting at multiMesh. Since the schema carries the full burden, the baseline score of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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 tool's purpose with specific verbs ('generate', 'creates') and resources ('FDS mesh', 'building geometry'), and distinguishes it from siblings like 'bulc_create_mesh' by emphasizing automation and optimization for all rooms and walls. It explicitly mentions multi-level building support, which differentiates it from basic mesh creation tools.

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

Usage Guidelines3/5

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

The description implies usage context by mentioning 'single mesh or multiple meshes for multi-level buildings', which suggests when to use multiMesh parameter. However, it lacks explicit guidance on when to choose this tool over alternatives like 'bulc_create_mesh' or prerequisites such as needing existing geometry. No clear exclusions or named alternatives are provided.

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