Skip to main content
Glama
using76
by using76

bulc_open_result_viewer

View fire simulation results from SMV files or recent simulations to analyze building design performance in 3D.

Instructions

Open the FDS result viewer window. Loads simulation results from the specified SMV file or last simulation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smvPathNoPath to .smv file. Default: auto-detect from last simulation
loadGeometryNoLoad 3D geometry (OBJ file). Default: true

Implementation Reference

  • Handler case that executes the bulc_open_result_viewer tool: validates input with Zod and sends 'open_result_viewer' command to BULC client.
    case "bulc_open_result_viewer": {
      const validated = OpenResultViewerSchema.parse(args);
      result = await client.sendCommand({
        action: "open_result_viewer",
        params: validated,
      });
      break;
    }
  • Zod input validation schema for bulc_open_result_viewer tool.
    const OpenResultViewerSchema = z.object({
      smvPath: z.string().optional(),
      loadGeometry: z.boolean().optional(),
    });
  • Tool definition and registration in resultTools array, including name, description, MCP inputSchema, and annotations.
      name: "bulc_open_result_viewer",
      description:
        "Open the FDS result viewer window. " +
        "Loads simulation results from the specified SMV file or last simulation.",
      inputSchema: {
        type: "object" as const,
        properties: {
          smvPath: {
            type: "string",
            description: "Path to .smv file. Default: auto-detect from last simulation",
          },
          loadGeometry: {
            type: "boolean",
            description: "Load 3D geometry (OBJ file). Default: true",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
      },
    },
  • src/index.ts:124-132 (registration)
    Top-level dispatch/registration routes bulc_open_result_viewer calls to the handleResultTool function.
    if (
      name === "bulc_open_result_viewer" ||
      name === "bulc_list_result_datasets" ||
      name === "bulc_get_point_data" ||
      name === "bulc_run_aset_analysis" ||
      name === "bulc_generate_report"
    ) {
      return await handleResultTool(name, safeArgs);
    }
  • src/index.ts:40-51 (registration)
    Includes resultTools (containing bulc_open_result_viewer) in the full list of tools advertised to MCP clients via ListToolsRequest.
    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
    ];
Behavior3/5

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

Annotations indicate this is not read-only and not destructive, but the description adds context about opening a viewer window and loading results, which suggests a UI interaction rather than a data mutation. It doesn't disclose behavioral traits like whether it blocks other operations, requires specific permissions, or has side effects beyond what annotations cover.

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 ('Open the FDS result viewer window') and adds necessary detail about loading sources. There is no wasted verbiage, making it appropriately sized for its purpose.

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 moderate complexity (opening a viewer with two optional parameters), annotations cover safety aspects, and schema fully describes inputs. The description adequately explains the tool's purpose and loading behavior. However, without an output schema, it doesn't clarify what happens after opening (e.g., success indication or error handling), leaving a minor gap.

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, fully documenting both parameters. The description adds no additional parameter semantics beyond implying 'smvPath' defaults to auto-detection, which is already stated in the schema. This meets the baseline for high schema coverage.

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 ('Open the FDS result viewer window') and resource ('simulation results'), specifying it loads from an SMV file or last simulation. It distinguishes from siblings like 'bulc_open_evac_viewer' by focusing on FDS results rather than evacuation results, though it doesn't explicitly contrast them.

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 loading from 'specified SMV file or last simulation', suggesting it's for viewing FDS simulation results. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'bulc_get_fds_data' or 'bulc_preview_fds', nor does it mention prerequisites or exclusions.

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