Skip to main content
Glama
using76
by using76

bulc_run_aset_analysis

Read-only

Analyze building egress safety by evaluating temperature, visibility, and gas levels at exit locations to determine Available Safe Egress Time.

Instructions

Run ASET (Available Safe Egress Time) analysis at a specified exit location. Evaluates safety criteria: temperature <60C, visibility >5m, CO <1400ppm, CO2 <5%, O2 >15%.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exitXYesExit X coordinate in meters
exitYYesExit Y coordinate in meters
exitZNoExit Z coordinate in meters. Default: 1.8 (breathing height)
criteriaNoCustom safety criteria (optional)

Implementation Reference

  • Handler logic for the 'bulc_run_aset_analysis' tool: validates input arguments using RunAsetAnalysisSchema and sends the 'run_aset_analysis' command to the BULC client.
    case "bulc_run_aset_analysis": {
      const validated = RunAsetAnalysisSchema.parse(args);
      result = await client.sendCommand({
        action: "run_aset_analysis",
        params: validated,
      });
      break;
    }
  • Tool definition including name, description, input schema, and annotations for 'bulc_run_aset_analysis'.
    {
      name: "bulc_run_aset_analysis",
      description:
        "Run ASET (Available Safe Egress Time) analysis at a specified exit location. " +
        "Evaluates safety criteria: temperature <60C, visibility >5m, CO <1400ppm, CO2 <5%, O2 >15%.",
      inputSchema: {
        type: "object" as const,
        properties: {
          exitX: {
            type: "number",
            description: "Exit X coordinate in meters",
          },
          exitY: {
            type: "number",
            description: "Exit Y coordinate in meters",
          },
          exitZ: {
            type: "number",
            description: "Exit Z coordinate in meters. Default: 1.8 (breathing height)",
          },
          criteria: {
            type: "object",
            description: "Custom safety criteria (optional)",
            properties: {
              maxTemperature: {
                type: "number",
                description: "Max safe temperature in Celsius. Default: 60",
              },
              minVisibility: {
                type: "number",
                description: "Min visibility in meters. Default: 5",
              },
              maxCo: {
                type: "number",
                description: "Max CO in ppm. Default: 1400",
              },
              maxCo2: {
                type: "number",
                description: "Max CO2 in percent. Default: 5",
              },
              minO2: {
                type: "number",
                description: "Min O2 in percent. Default: 15",
              },
            },
          },
        },
        required: ["exitX", "exitY"],
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • Zod schema for input validation of the 'bulc_run_aset_analysis' tool.
    const RunAsetAnalysisSchema = z.object({
      exitX: z.number(),
      exitY: z.number(),
      exitZ: z.number().optional(),
      criteria: z.object({
        maxTemperature: z.number().optional(),
        minVisibility: z.number().positive().optional(),
        maxCo: z.number().positive().optional(),
        maxCo2: z.number().positive().optional(),
        minO2: z.number().positive().optional(),
      }).optional(),
    });
  • src/index.ts:124-132 (registration)
    Routing registration in main server handler: directs 'bulc_run_aset_analysis' calls to handleResultTool.
    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_run_aset_analysis') in the full list of available tools served by 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
    ];
Behavior4/5

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

Annotations indicate read-only and non-destructive operations, which the description aligns with by describing an analysis that evaluates criteria without implying modification. The description adds valuable context about the specific safety criteria evaluated (temperature, visibility, CO, CO2, O2), which goes beyond the annotations and helps the agent understand the tool's behavior.

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, dense sentence that efficiently conveys the tool's purpose and key details (exit location, safety criteria with specific thresholds). Every part earns its place with no wasted words, making it easy to parse and front-loaded with essential information.

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?

For a read-only analysis tool with no output schema, the description adequately covers the action and criteria but lacks details on output format (e.g., time values, pass/fail status) or integration with other tools. Given the complexity of safety analysis, more context on results or dependencies would enhance completeness.

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 parameters (exit coordinates and optional criteria). The description mentions 'specified exit location' and 'safety criteria' but doesn't add semantic details beyond what the schema provides, such as coordinate system context or criteria interpretation, meeting the baseline for high schema coverage.

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 ('Run ASET analysis') and resource ('at a specified exit location'), with detailed safety criteria. It distinguishes itself from siblings like 'bulc_run_evac' or 'bulc_run_fds' by focusing on ASET analysis rather than evacuation or fire dynamics simulations.

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. It doesn't mention prerequisites (e.g., needing simulation data), exclusions, or how it relates to sibling tools like 'bulc_get_evac_result' or 'bulc_get_fds_data', leaving the agent without context for tool selection.

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