Skip to main content
Glama
using76
by using76

bulc_list_evac_agents

Read-only

List evacuation agents with positions and properties in BULC Building Designer to analyze fire simulation data by filtering floor levels or rooms.

Instructions

List all evacuation agents with their positions and properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoFilter by floor level. Omit for all levels.
roomNoFilter by room name or ID

Implementation Reference

  • Handler logic for 'bulc_list_evac_agents' tool: validates input using ListEvacAgentsSchema and sends 'list_evac_agents' command to BULC client.
    case "bulc_list_evac_agents": {
      const validated = ListEvacAgentsSchema.parse(args);
      result = await client.sendCommand({
        action: "list_evac_agents",
        params: validated,
      });
      break;
  • Zod schema for validating input parameters (level, room) of the 'bulc_list_evac_agents' tool.
    const ListEvacAgentsSchema = z.object({
      level: z.number().int().optional(),
      room: z.string().optional(),
    });
  • Tool registration/definition in evacTools array, providing name, description, inputSchema for MCP tool listing.
    {
      name: "bulc_list_evac_agents",
      description:
        "List all evacuation agents with their positions and properties.",
      inputSchema: {
        type: "object" as const,
        properties: {
          level: {
            type: "integer",
            description: "Filter by floor level. Omit for all levels.",
          },
          room: {
            type: "string",
            description: "Filter by room name or ID",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:135-137 (registration)
    Dispatch routing in main MCP handler: routes 'bulc_*evac*' tools to handleEvacTool.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
  • src/index.ts:54-58 (registration)
    MCP server registration of allTools (includes evacTools) for listTools request.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
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 that it lists 'all' evacuation agents, implying completeness, but doesn't provide additional behavioral context like pagination, performance characteristics, or data freshness. No contradiction with annotations exists.

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 ('List all evacuation agents') and adds clarifying details ('with their positions and properties'). There is no wasted wording, and it's appropriately sized for a simple list operation.

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 the tool's low complexity (read-only list operation), rich annotations (readOnlyHint, destructiveHint), and full schema coverage, the description is adequate but minimal. It lacks output details (no output schema provided) and doesn't explain relationships with sibling tools, which could help in tool selection. For a basic list tool, it meets minimum requirements but misses opportunities for fuller context.

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?

Schema description coverage is 100%, with both parameters ('level' and 'room') clearly documented in the input schema. The description doesn't add any parameter-specific information beyond what the schema provides, such as examples or constraints on filtering behavior. With high schema coverage, the baseline score of 3 is appropriate.

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 action ('List all evacuation agents') and the scope ('with their positions and properties'), which is specific and informative. It distinguishes from some siblings like 'bulc_place_evac_agents' (create) or 'bulc_set_agent_properties' (modify), but could more explicitly differentiate from 'bulc_get_evac_result' or 'bulc_get_evac_summary' which might also retrieve agent data in different contexts.

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. It doesn't mention siblings like 'bulc_get_evac_result' or 'bulc_get_evac_summary' that might provide overlapping or complementary evacuation agent information, nor does it specify prerequisites or typical use cases (e.g., for inventory checking vs. simulation analysis).

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