Skip to main content
Glama
using76
by using76

bulc_clear_evac_agents

Destructive

Clear evacuation agents from specific rooms or entire building levels in fire simulation software to reset or modify evacuation scenarios.

Instructions

Clear evacuation agents from specified room or all rooms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomNoRoom name or ID to clear. Omit to clear all.
levelNoFloor level to clear. Omit to clear all levels.

Implementation Reference

  • Handler for the bulc_clear_evac_agents tool: validates input schema and sends 'clear_evac_agents' command to BULC client via getBulcClient().
    case "bulc_clear_evac_agents": {
      const validated = ClearEvacAgentsSchema.parse(args);
      result = await client.sendCommand({
        action: "clear_evac_agents",
        params: validated,
      });
      break;
    }
  • Tool registration in evacTools export array, defining name, description, input schema, and annotations for MCP server.
    {
      name: "bulc_clear_evac_agents",
      description:
        "Clear evacuation agents from specified room or all rooms.",
      inputSchema: {
        type: "object" as const,
        properties: {
          room: {
            type: "string",
            description: "Room name or ID to clear. Omit to clear all.",
          },
          level: {
            type: "integer",
            description: "Floor level to clear. Omit to clear all levels.",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema used in the handler for input parameters (room and level).
    const ClearEvacAgentsSchema = z.object({
      room: z.string().optional(),
      level: z.number().int().optional(),
    });
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write operation. The description adds minimal behavioral context beyond this - it clarifies the scope ('room or all rooms') but doesn't mention side effects, permissions needed, or what happens to cleared agents. With annotations covering the safety profile, a 3 is appropriate.

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 immediately communicates the core functionality. Every word earns its place with zero waste or redundancy.

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 destructive operation with good annotations but no output schema, the description is minimally adequate. It covers what the tool does but lacks important context about consequences, timing, or relationships to other tools in the evacuation workflow. The annotations help but don't fully compensate for the description's gaps.

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 ('room' and 'level') well-documented in the schema. The description implies the 'room' parameter's optional nature ('Omit to clear all') but doesn't add meaningful semantic context beyond what the schema already provides. Baseline 3 is correct when schema does the heavy lifting.

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 ('clear evacuation agents') and target ('from specified room or all rooms'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'bulc_list_evac_agents' or 'bulc_place_evac_agents', which would require a 5.

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 prerequisites, timing considerations, or relationships to other tools like 'bulc_list_evac_agents' (for viewing agents) or 'bulc_place_evac_agents' (for adding them).

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