Skip to main content
Glama
using76
by using76

bulc_get_evac_summary

Read-only

Retrieve evacuation simulation results including total time, individual exit times, and statistical analysis for building safety assessment.

Instructions

Get evacuation result summary including total time, per-agent exit times, and statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case within handleEvacTool function that executes the tool by sending the 'get_evac_summary' action command to the BULC client with empty parameters.
    case "bulc_get_evac_summary": {
      result = await client.sendCommand({
        action: "get_evac_summary",
        params: {},
      });
      break;
    }
  • Tool specification defining the name, description, input schema (empty object since no parameters), and annotations (read-only).
    {
      name: "bulc_get_evac_summary",
      description:
        "Get evacuation result summary including total time, " +
        "per-agent exit times, and statistics.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:40-51 (registration)
    Aggregates evacTools (which includes bulc_get_evac_summary) into allTools, which is returned by the MCP ListToolsRequestHandler to register all available 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
    ];
  • src/index.ts:135-137 (registration)
    Top-level MCP CallToolRequestHandler routes calls to bulc_get_evac_summary (matching 'bulc_*evac*') to the handleEvacTool dispatcher.
    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 already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds context by specifying the type of data returned (summary statistics), which is useful beyond annotations. However, it doesn't mention potential limitations like requiring a loaded result or error conditions, so it adds some but not comprehensive behavioral insight.

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 front-loads the core purpose ('Get evacuation result summary') and lists key output details. There is no wasted verbiage, making it easy to parse and understand quickly, which is ideal for a tool with no parameters.

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 has 0 parameters, annotations covering safety, and no output schema, the description is reasonably complete. It explains what the tool does and what data to expect. However, it could be more comprehensive by clarifying dependencies (e.g., requires a simulation result) or output format, slightly reducing completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately avoids discussing parameters, focusing instead on the tool's output. This aligns well with the schema, earning a high score as it doesn't introduce unnecessary details.

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 tool's purpose with specific verbs ('Get evacuation result summary') and resources ('evacuation result'), and lists the data included ('total time, per-agent exit times, and statistics'). It distinguishes itself from siblings like 'bulc_get_evac_result' by focusing on a summary rather than full results, though the distinction could be more explicit.

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

Usage Guidelines3/5

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

The description implies usage after an evacuation simulation (e.g., 'result summary'), suggesting it should be used when summary data is needed. However, it lacks explicit guidance on when to use this tool versus alternatives like 'bulc_get_evac_result' or prerequisites such as needing a completed simulation, leaving room for ambiguity.

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