Skip to main content
Glama
using76
by using76

bulc_save_evac_result

Destructive

Save evacuation simulation results from BULC fire analysis to a .evac file for documentation and further analysis.

Instructions

Save current evacuation results to a .evac file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputPathNoOutput path for .evac file. Default: project folder
filenameNoFilename without extension. Default: project name

Implementation Reference

  • Handler case in handleEvacTool function that executes the tool: validates input schema and sends 'save_evac_result' action command to BULC client.
    case "bulc_save_evac_result": {
      const validated = SaveEvacResultSchema.parse(args);
      result = await client.sendCommand({
        action: "save_evac_result",
        params: validated,
      });
      break;
    }
  • Tool definition in evacTools array: includes name, description, inputSchema for MCP tool list.
    {
      name: "bulc_save_evac_result",
      description: "Save current evacuation results to a .evac file.",
      inputSchema: {
        type: "object" as const,
        properties: {
          outputPath: {
            type: "string",
            description: "Output path for .evac file. Default: project folder",
          },
          filename: {
            type: "string",
            description: "Filename without extension. Default: project name",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod input validation schema for the tool arguments.
    const SaveEvacResultSchema = z.object({
      outputPath: z.string().optional(),
      filename: z.string().optional(),
    });
  • src/index.ts:135-148 (registration)
    Dispatch logic in main tool handler that routes 'bulc_save_evac_result' calls to the evac handler.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
    // Also handle agent_properties, rset_report, exit_assignment, premovement, fire_coupling as EVAC tools
    if (
      name === "bulc_set_agent_properties" ||
      name === "bulc_generate_rset_report" ||
      name === "bulc_save_evac_result" ||
      name === "bulc_set_exit_assignment" ||
      name === "bulc_set_premovement_time" ||
      name === "bulc_set_fire_coupling"
    ) {
      return await handleEvacTool(name, safeArgs);
    }
  • src/index.ts:54-58 (registration)
    Registers all tools including evacTools (containing bulc_save_evac_result) for MCP listTools request.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by implying a write operation ('Save'). The description adds context by specifying the output format ('.evac file') and that it saves 'current' results, which isn't covered by annotations. However, it doesn't detail side effects like overwriting files or requiring prior simulation results.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core action and outcome, making it easy to parse quickly.

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 destructive write tool with no output schema, the description is minimally adequate. It specifies what is saved and the file format, but lacks details on error conditions, dependencies (e.g., requires existing evacuation results), or output behavior. Given the annotations cover safety aspects, it meets a basic threshold but could be more informative.

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?

Schema description coverage is 100%, with both parameters well-documented in the schema (outputPath and filename). The description adds no additional parameter semantics beyond implying the tool saves results, which is already clear from the tool name and schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 ('Save') and target ('current evacuation results to a .evac file'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'bulc_save' or 'bulc_export_fds', which might have overlapping save/export functionality.

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. With siblings like 'bulc_save' (general save), 'bulc_export_fds' (FDS export), and 'bulc_load_evac_result' (load counterpart), there's no indication of context, prerequisites, or exclusions for this specific save operation.

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