Skip to main content
Glama
using76
by using76

bulc_list_meshes

Read-only

Retrieve all FDS computational meshes with IDs, dimensions, cell sizes, and bounding coordinates for fire simulation analysis in building design.

Instructions

Get a list of all FDS computational meshes. Returns mesh IDs, dimensions, cell sizes, and bounding coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for bulc_list_meshes within the handleMeshTool switch statement. Sends 'list_meshes' action to BULC client.
    case "bulc_list_meshes": {
      result = await client.sendCommand({
        action: "list_meshes",
        params: {},
      });
      break;
    }
  • Tool schema definition for bulc_list_meshes, including name, description, empty input schema (no parameters required), and read-only annotation.
    {
      name: "bulc_list_meshes",
      description:
        "Get a list of all FDS computational meshes. " +
        "Returns mesh IDs, dimensions, cell sizes, and bounding coordinates.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:40-51 (registration)
    Includes meshTools (containing bulc_list_meshes schema) in the allTools array returned by ListToolsRequestHandler.
    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:97-99 (registration)
    Routes calls to bulc_list_meshes (and other mesh tools) to the handleMeshTool function in the MCP server's CallToolRequestHandler.
    if (name.startsWith("bulc_") && name.includes("mesh")) {
      return await handleMeshTool(name, safeArgs);
    }
Behavior4/5

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

Annotations indicate read-only and non-destructive behavior, which the description aligns with by using 'Get a list'. The description adds value by specifying the return content (mesh IDs, dimensions, cell sizes, bounding coordinates), providing useful context beyond annotations. No contradictions exist.

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, efficient sentence that front-loads the core action ('Get a list of all FDS computational meshes') and follows with specific return details. Every word contributes to understanding, with no wasted verbiage.

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 read-only list tool with no parameters and no output schema, the description is nearly complete: it states the action, resource, and return data. It could slightly improve by mentioning if the list is paginated or sorted, but overall it provides sufficient context for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description does not need to compensate for parameter gaps, and it appropriately focuses on output semantics without redundant parameter details.

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 verb ('Get a list of all') and resource ('FDS computational meshes'), distinguishing it from siblings like bulc_delete_mesh or bulc_modify_mesh. It specifies the scope as 'all' meshes, making the purpose explicit and distinct.

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 for retrieving mesh information, but does not explicitly state when to use this tool versus alternatives like bulc_get_fds_data or bulc_list_result_datasets. No exclusions or prerequisites are mentioned, leaving usage context partially inferred.

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