Skip to main content
Glama
using76
by using76

bulc_get_evac_status

Read-only

Check evacuation simulation progress, view evacuated occupant count, and monitor estimated completion time for building safety analysis.

Instructions

Get current evacuation simulation status including progress, evacuated count, and estimated completion time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic for bulc_get_evac_status: sends 'get_evac_status' action command to BULC client with no parameters and returns the response.
    case "bulc_get_evac_status": {
      result = await client.sendCommand({
        action: "get_evac_status",
        params: {},
      });
      break;
    }
  • Tool schema definition: empty input schema (no parameters), read-only, non-destructive.
    {
      name: "bulc_get_evac_status",
      description:
        "Get current evacuation simulation status including progress, " +
        "evacuated count, and estimated completion time.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:134-137 (registration)
    MCP server dispatcher registration: routes all 'bulc_*evac*' tools, including bulc_get_evac_status, to the evac handler.
    // EVAC tools
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
  • src/index.ts:50-50 (registration)
    Includes evacTools (containing bulc_get_evac_status) in the full MCP tools list for tool discovery.
    ...evacTools,         // 25 tools: setup, stairs, agents, run, results, advanced features
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds useful context by specifying what data is returned (progress, evacuated count, completion time), which goes beyond the annotations. However, it doesn't mention potential limitations like real-time updates, caching behavior, or error conditions.

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, well-structured sentence that efficiently conveys the tool's purpose and key return data. It's front-loaded with the main action and includes specific details without unnecessary elaboration, making it easy for an agent 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 read-only tool with no parameters and no output schema, the description adequately covers the basic purpose and return data. However, it lacks details on output format (e.g., structured data vs. raw text), potential errors, or how it integrates with sibling tools like 'bulc_run_evac' or 'bulc_stop_evac', leaving some contextual gaps.

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 doesn't discuss parameters, focusing instead on the tool's output semantics. This meets the baseline of 4 for tools with no 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 tool's purpose with a specific verb ('Get') and resource ('evacuation simulation status'), including key data points like progress, evacuated count, and estimated completion time. However, it doesn't explicitly differentiate from sibling tools like 'bulc_get_evac_result' or 'bulc_get_evac_summary', which might provide overlapping or related information.

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. Given sibling tools like 'bulc_get_evac_result' and 'bulc_get_evac_summary', there's no indication of when this status check is appropriate versus retrieving results or summaries, leaving the agent to guess based on tool names alone.

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