Skip to main content
Glama
using76
by using76

bulc_list_evac_stairs

Read-only

Lists all configured evacuation stairs for multi-level buildings in BULC fire simulation software to support safety planning and building design.

Instructions

List all configured evacuation stairs for multi-level buildings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler case that executes the tool logic by dispatching a 'list_evac_stairs' command to the BULC client.
    case "bulc_list_evac_stairs": {
      result = await client.sendCommand({
        action: "list_evac_stairs",
        params: {},
      });
      break;
    }
  • Tool schema definition including name, description, input schema (empty object), and annotations indicating read-only.
    {
      name: "bulc_list_evac_stairs",
      description:
        "List all configured evacuation stairs for multi-level buildings.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:40-51 (registration)
    Includes evacTools (containing bulc_list_evac_stairs) in the complete list of MCP tools served via ListToolsRequest.
    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:54-58 (registration)
    Registers the handler for listing all tools, exposing bulc_list_evac_stairs schema to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • src/index.ts:134-137 (registration)
    Routes tool calls matching 'bulc_*evac*' (including bulc_list_evac_stairs) to the evac handler function.
    // EVAC tools
    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 that it lists 'configured' evacuation stairs, which implies it returns pre-set data rather than real-time status, but doesn't disclose behavioral traits like pagination, format, or error handling. With annotations covering safety, it adds minimal context beyond them.

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?

Single sentence, front-loaded with the core action ('List all configured evacuation stairs'), and efficiently specifies the scope ('for multi-level buildings'). No wasted words or redundancy, making it highly concise and well-structured.

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?

Given 0 parameters, annotations indicating a safe read, and no output schema, the description is adequate but minimal. It states what the tool does but lacks details on return format, error cases, or integration with other tools like 'bulc_setup_evac_stair'. For a simple list tool, it's complete enough but could be more informative.

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?

There are 0 parameters, and schema description coverage is 100%, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, as there are none to explain. Baseline for 0 parameters is 4, since no compensation is needed.

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 verb ('List') and resource ('all configured evacuation stairs'), specifying it's for multi-level buildings. It distinguishes from siblings like 'bulc_list_evac_exits' or 'bulc_list_rooms' by focusing on stairs, but doesn't explicitly contrast with them. Purpose is specific but lacks explicit sibling differentiation.

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?

No guidance on when to use this tool versus alternatives like 'bulc_get_evac_result' or 'bulc_list_evac_agents'. The description implies usage for listing evacuation stairs, but doesn't specify context, prerequisites, or exclusions. It's a basic statement without operational context.

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