Skip to main content
Glama
using76
by using76

bulc_stop_evac

Destructive

Stop an active evacuation simulation in BULC fire simulation software to control building safety analysis workflows.

Instructions

Stop a running evacuation simulation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'bulc_stop_evac' tool within the handleEvacTool function's switch statement. It forwards the request to the BULC client by sending a 'stop_evac' action with empty parameters.
    case "bulc_stop_evac": {
      result = await client.sendCommand({
        action: "stop_evac",
        params: {},
      });
      break;
    }
  • The tool registration object in the evacTools export array, defining the name, description, empty input schema, and annotations (destructive operation). This is included in the MCP tool list.
    {
      name: "bulc_stop_evac",
      description: "Stop a running evacuation simulation.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • The input schema for 'bulc_stop_evac', specifying an empty object (no parameters required). Part of the tool registration.
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:39-51 (registration)
    The main allTools array in the MCP server entry point, which spreads evacTools (containing bulc_stop_evac) into the complete tool list returned by ListToolsRequestHandler.
    // Combine all tools
    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
    ];
  • Top-level tool dispatch logic in the MCP CallToolRequestHandler that routes 'bulc_stop_evac' (matches 'bulc_' and 'evac') to the specific handleEvacTool function.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, confirming this is a mutation that may cause irreversible changes. The description adds context by specifying it stops 'a running evacuation simulation,' which aligns with the destructive nature. However, it doesn't detail side effects like data loss or state changes beyond stopping.

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, clear sentence with no wasted words. It's front-loaded with the core action and target, 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 tool with no output schema, the description adequately states what it does but lacks details on outcomes (e.g., what 'stop' entails, error conditions, or return values). Annotations cover safety, but more behavioral context would help, given the complexity implied by sibling tools.

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?

With 0 parameters and 100% schema description coverage, the input schema fully documents the lack of inputs. The description doesn't need to add parameter details, but it could mention if any implicit context (e.g., current simulation) is required. Baseline is 4 for zero parameters.

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 ('Stop') and the target ('a running evacuation simulation'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'bulc_stop_fds' (which stops a different simulation type), leaving some ambiguity about scope.

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, prerequisites (e.g., whether an evacuation simulation must be running), or consequences of stopping. It mentions 'running' but doesn't clarify what happens if invoked when no simulation is active.

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