Skip to main content
Glama
using76
by using76

bulc_create_mesh

Destructive

Define a computational domain for fire simulation by creating an FDS mesh with specified dimensions and cell counts.

Instructions

Create a new FDS computational mesh with specified dimensions and cell count. The mesh defines the computational domain for fire simulation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meshIdNoMesh identifier. Default: MESH_1, MESH_2, etc.
xMinYesMinimum X coordinate in meters
xMaxYesMaximum X coordinate in meters
yMinYesMinimum Y coordinate in meters
yMaxYesMaximum Y coordinate in meters
zMinNoMinimum Z coordinate in meters. Default: 0
zMaxYesMaximum Z coordinate in meters
iCellsNoNumber of cells in X direction
jCellsNoNumber of cells in Y direction
kCellsNoNumber of cells in Z direction
cellSizeNoUniform cell size in meters (alternative to specifying cell counts). If provided, cell counts will be calculated automatically.

Implementation Reference

  • The handler logic for the 'bulc_create_mesh' tool. Validates input parameters using CreateMeshSchema and sends a 'create_mesh' command to the BULC client via getBulcClient().
    case "bulc_create_mesh": {
      const validated = CreateMeshSchema.parse(args);
      result = await client.sendCommand({
        action: "create_mesh",
        params: validated,
      });
      break;
    }
  • Zod schema used for runtime validation of input arguments to the bulc_create_mesh tool handler.
    const CreateMeshSchema = z.object({
      meshId: z.string().optional(),
      xMin: z.number(),
      xMax: z.number(),
      yMin: z.number(),
      yMax: z.number(),
      zMin: z.number().optional(),
      zMax: z.number(),
      iCells: z.number().int().positive().optional(),
      jCells: z.number().int().positive().optional(),
      kCells: z.number().int().positive().optional(),
      cellSize: z.number().positive().optional(),
    });
  • The tool definition object for 'bulc_create_mesh' exported in meshTools array, which is included in the global allTools list and registered with the MCP server via ListToolsRequestHandler.
    {
      name: "bulc_create_mesh",
      description:
        "Create a new FDS computational mesh with specified dimensions and cell count. " +
        "The mesh defines the computational domain for fire simulation.",
      inputSchema: {
        type: "object" as const,
        properties: {
          meshId: {
            type: "string",
            description: "Mesh identifier. Default: MESH_1, MESH_2, etc.",
          },
          xMin: {
            type: "number",
            description: "Minimum X coordinate in meters",
          },
          xMax: {
            type: "number",
            description: "Maximum X coordinate in meters",
          },
          yMin: {
            type: "number",
            description: "Minimum Y coordinate in meters",
          },
          yMax: {
            type: "number",
            description: "Maximum Y coordinate in meters",
          },
          zMin: {
            type: "number",
            description: "Minimum Z coordinate in meters. Default: 0",
          },
          zMax: {
            type: "number",
            description: "Maximum Z coordinate in meters",
          },
          iCells: {
            type: "integer",
            description: "Number of cells in X direction",
          },
          jCells: {
            type: "integer",
            description: "Number of cells in Y direction",
          },
          kCells: {
            type: "integer",
            description: "Number of cells in Z direction",
          },
          cellSize: {
            type: "number",
            description: "Uniform cell size in meters (alternative to specifying cell counts). " +
              "If provided, cell counts will be calculated automatically.",
          },
        },
        required: ["xMin", "xMax", "yMin", "yMax", "zMax"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Routing logic in the main MCP CallToolRequestHandler that dispatches 'bulc_*_mesh' tools to the handleMeshTool function.
    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 readOnlyHint=false and destructiveHint=true, which already signal that this is a mutation tool with potential destructive effects. The description adds value by clarifying that the mesh 'defines the computational domain for fire simulation', implying it's foundational for simulations. However, it doesn't detail what 'destructive' entails (e.g., overwriting existing meshes, affecting simulations) or any side effects like performance impacts or validation needs.

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, well-structured sentence that front-loads the core action ('Create a new FDS computational mesh') and efficiently adds context ('with specified dimensions and cell count' and 'defines the computational domain for fire simulation'). Every word contributes meaning without redundancy or fluff, making it highly concise and clear.

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 complexity (11 parameters, destructive mutation) and lack of an output schema, the description is minimally adequate. It explains what the tool does and the mesh's purpose, but doesn't cover critical aspects like what the tool returns (e.g., a confirmation, mesh ID, error details), how it integrates with other tools (e.g., 'bulc_run_fds'), or the implications of the destructive hint. With annotations providing safety cues, it's complete enough for basic use but lacks depth for informed agent decisions.

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 input schema fully documents all 11 parameters, including their types, defaults, and purposes. The description adds no parameter-specific details beyond what's in the schema, such as explaining interactions between 'cellSize' and 'iCells/jCells/kCells'. Thus, it meets the baseline of 3 for high schema coverage without extra semantic value.

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 ('Create a new FDS computational mesh') and the resource ('mesh'), distinguishing it from siblings like 'bulc_auto_mesh' (which likely automates mesh creation) or 'bulc_modify_mesh' (which modifies existing meshes). It also explains the mesh's purpose ('defines the computational domain for fire simulation'), adding context beyond just the action.

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 like 'bulc_auto_mesh' or 'bulc_modify_mesh'. It mentions the mesh's role in fire simulation, but does not specify prerequisites, dependencies, or scenarios where manual mesh creation is preferred over automated methods. This leaves the agent without clear usage context.

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