Skip to main content
Glama
using76
by using76

bulc_get_evac_settings

Read-only

Retrieve current evacuation simulation settings for building design, including model types, agent parameters, and stair configurations.

Instructions

Get current EVAC simulation settings including model type, agent parameters, and stair configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic within handleEvacTool switch statement that executes the tool by sending a 'get_evac_settings' command to the BULC client with empty parameters.
    case "bulc_get_evac_settings": {
      result = await client.sendCommand({
        action: "get_evac_settings",
        params: {},
      });
      break;
  • Input schema definition for the tool, specifying an empty object since no input parameters are required.
    inputSchema: {
      type: "object" as const,
      properties: {},
    },
  • Tool definition and registration within the evacTools array exported from the evac module.
    {
      name: "bulc_get_evac_settings",
      description:
        "Get current EVAC simulation settings including model type, " +
        "agent parameters, and stair configurations.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:39-58 (registration)
    Global tool registration: evacTools are included in allTools, which is returned by the MCP server's list tools handler.
    // 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
    ];
    
    // List available tools
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • Main MCP tool call dispatcher that routes calls to tools matching 'bulc_*evac*' pattern to the evac-specific handleEvacTool function.
    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, so the agent knows this is a safe read operation. The description adds context by specifying what settings are retrieved (model type, agent parameters, stair configurations), which is useful beyond the annotations. However, it does not disclose behavioral traits like rate limits, authentication needs, or response format, which could be helpful given no output schema.

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 purpose ('Get current EVAC simulation settings') and elaborates with specifics ('including model type, agent parameters, and stair configurations'). Every word contributes to clarity without waste, making it appropriately sized 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 simplicity (0 parameters, read-only, non-destructive) and lack of output schema, the description is complete enough for a retrieval tool. It specifies what settings are fetched, which compensates for the missing output schema. However, it could be more complete by hinting at the return format or data structure, though this is not critical for basic understanding.

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 tool has 0 parameters, and schema description coverage is 100%, so there is no need for parameter details in the description. The description appropriately does not discuss parameters, focusing instead on the tool's purpose. A baseline of 4 is applied for zero-parameter tools, as it avoids unnecessary information.

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 action ('Get') and the specific resource ('current EVAC simulation settings'), including what those settings encompass ('model type, agent parameters, and stair configurations'). It distinguishes itself from siblings like 'bulc_get_evac_result' or 'bulc_get_evac_status' by focusing on configuration settings rather than results or status.

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 when current EVAC simulation settings are needed, but it does not explicitly state when to use this tool versus alternatives (e.g., 'bulc_get_simulation_settings' for general settings or 'bulc_set_evac_model' for setting values). No exclusions or prerequisites are mentioned, leaving usage context implied rather than explicit.

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