Skip to main content
Glama
using76
by using76

bulc_open_evac_viewer

Visualize evacuation simulation results in 3D with timeline playback to analyze agent movement and building safety performance.

Instructions

Open the 3D evacuation result viewer window. Displays agents on the building model with timeline playback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
evacPathNoPath to .evac file. Default: auto-detect from last simulation
objPathNoPath to .obj 3D model file. Default: auto-detect
autoPlayNoStart playback automatically. Default: false
playbackSpeedNoPlayback speed multiplier (0.25 to 8.0). Default: 1.0
agentScaleNoAgent display scale (0.5 to 5.0). Default: 1.0

Implementation Reference

  • Handler case for 'bulc_open_evac_viewer': validates input schema and sends 'open_evac_viewer' action command to BULC client.
    case "bulc_open_evac_viewer": {
      const validated = OpenEvacViewerSchema.parse(args);
      result = await client.sendCommand({
        action: "open_evac_viewer",
        params: validated,
      });
      break;
    }
  • Zod input validation schema for bulc_open_evac_viewer tool.
    const OpenEvacViewerSchema = z.object({
      evacPath: z.string().optional(),
      objPath: z.string().optional(),
      autoPlay: z.boolean().optional(),
      playbackSpeed: z.number().min(0.25).max(8.0).optional(),
      agentScale: z.number().min(0.5).max(5.0).optional(),
    });
  • MCP tool registration/definition for bulc_open_evac_viewer including description and input schema.
    {
      name: "bulc_open_evac_viewer",
      description:
        "Open the 3D evacuation result viewer window. " +
        "Displays agents on the building model with timeline playback.",
      inputSchema: {
        type: "object" as const,
        properties: {
          evacPath: {
            type: "string",
            description: "Path to .evac file. Default: auto-detect from last simulation",
          },
          objPath: {
            type: "string",
            description: "Path to .obj 3D model file. Default: auto-detect",
          },
          autoPlay: {
            type: "boolean",
            description: "Start playback automatically. Default: false",
          },
          playbackSpeed: {
            type: "number",
            description: "Playback speed multiplier (0.25 to 8.0). Default: 1.0",
          },
          agentScale: {
            type: "number",
            description: "Agent display scale (0.5 to 5.0). Default: 1.0",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
      },
    },
  • src/index.ts:40-51 (registration)
    Aggregates evacTools (including bulc_open_evac_viewer) into allTools for MCP ListTools response.
    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:135-137 (registration)
    Routes tool calls matching 'bulc_*evac*' (including bulc_open_evac_viewer) to handleEvacTool.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which the description doesn't contradict, as 'Open... viewer window' implies a non-destructive, interactive action. The description adds context about displaying agents and timeline playback, which goes beyond annotations, but it doesn't detail behavioral traits like window management, resource usage, or error handling, leaving some gaps in transparency.

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 extremely concise and front-loaded, consisting of two clear sentences that directly state the tool's purpose and functionality. Every word earns its place, with no redundancy or unnecessary elaboration, making it easy for an agent to quickly understand the core action.

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 moderate complexity (5 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks details on integration with other tools, expected outcomes, or error scenarios. With no output schema, it doesn't explain what the viewer returns or how to interact with it post-opening, leaving some contextual gaps.

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, with all parameters well-documented, so the description doesn't need to add parameter details. It doesn't provide additional semantics beyond the schema, such as explaining interactions between parameters or typical use cases, but this is acceptable given the high schema coverage, resulting in a baseline score.

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... viewer window') and what it displays ('Displays agents on the building model with timeline playback'), providing a specific verb and resource. However, it doesn't explicitly differentiate from the sibling 'bulc_open_result_viewer', which might be a related visualization tool, leaving some ambiguity about when to choose one over the other.

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_open_result_viewer' or other visualization tools in the sibling list. It lacks context about prerequisites, such as needing a completed evacuation simulation, and doesn't mention exclusions or typical workflows, leaving the agent to infer usage from the tool name alone.

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