Skip to main content
Glama
using76
by using76

bulc_run_evac

Destructive

Start evacuation simulation to analyze building safety using JuPedSim. Monitor progress with status checks for multi-level scenarios.

Instructions

Start evacuation simulation using JuPedSim. Returns immediately; use bulc_get_evac_status to monitor progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
multiLevelNoUse multi-level simulation with stairs. Default: auto-detect

Implementation Reference

  • Handler implementation for the 'bulc_run_evac' tool. It parses the input arguments using RunEvacSchema and sends the 'run_evac' action command to the BULC client via getBulcClient().
    case "bulc_run_evac": {
      const validated = RunEvacSchema.parse(args);
      result = await client.sendCommand({
        action: "run_evac",
        params: validated,
      });
      break;
    }
  • Tool definition object for 'bulc_run_evac' exported in evacTools array, including name, description, inputSchema for MCP tool discovery and validation.
    {
      name: "bulc_run_evac",
      description:
        "Start evacuation simulation using JuPedSim. " +
        "Returns immediately; use bulc_get_evac_status to monitor progress.",
      inputSchema: {
        type: "object" as const,
        properties: {
          multiLevel: {
            type: "boolean",
            description: "Use multi-level simulation with stairs. Default: auto-detect",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema used for runtime input validation in the handler for 'bulc_run_evac'.
    const RunEvacSchema = z.object({
      multiLevel: z.boolean().optional(),
    });
  • src/index.ts:54-58 (registration)
    MCP server registration of all tools (including 'bulc_run_evac' via evacTools spread into allTools) for the ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • src/index.ts:135-137 (registration)
    Routing logic in main MCP CallToolRequestHandler that dispatches 'bulc_run_evac' (and other evac tools) to the 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, which the description aligns with by implying a write operation ('Start'). The description adds valuable behavioral context beyond annotations: it discloses that the operation 'Returns immediately' (asynchronous behavior) and requires monitoring via another tool. No contradictions with annotations are present.

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 front-loaded with the core purpose in the first clause, followed by essential behavioral guidance. Both sentences earn their place by providing critical information without any wasted words, making it highly efficient and well-structured.

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 complexity (a simulation starter with destructive hints) and lack of output schema, the description is mostly complete: it covers purpose, behavior, and usage flow. However, it could slightly improve by hinting at prerequisites (e.g., needing setup before running) or error conditions, though not strictly required.

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 the parameter 'multiLevel' fully documented in the schema. The description does not add any parameter-specific details beyond what the schema provides, so it meets the baseline score of 3 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 ('Start evacuation simulation using JuPedSim') and resource ('evacuation simulation'), distinguishing it from siblings like bulc_stop_evac or bulc_validate_evac. It precisely communicates the core function without being vague or tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides when-to-use guidance by stating 'use bulc_get_evac_status to monitor progress,' naming a specific alternative tool for follow-up actions. This gives clear context on how this tool fits into a workflow with its sibling.

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