Skip to main content
Glama
using76
by using76

bulc_set_exit_assignment

Destructive

Configure evacuation agent exit selection strategy to optimize building evacuation flow using modes like nearest exit, shortest path, or balanced distribution.

Instructions

Set the exit assignment strategy for evacuation agents. Determines how agents choose which exit to use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesAssignment mode: 'NEAREST' (closest exit), 'SHORTEST_PATH' (shortest walking path), 'BALANCED' (balance exit flow), 'CUSTOM' (manual assignment)
balanceThresholdNoFor BALANCED mode: max agents per exit ratio difference. Default: 0.2
customAssignmentsNoFor CUSTOM mode: array of {agentIds: [...], exitId: '...'} assignments

Implementation Reference

  • Handler case for 'bulc_set_exit_assignment': parses input arguments with Zod schema and sends 'set_exit_assignment' command to BULC client.
    case "bulc_set_exit_assignment": {
      const validated = SetExitAssignmentSchema.parse(args);
      result = await client.sendCommand({
        action: "set_exit_assignment",
        params: validated,
      });
      break;
    }
  • Tool definition object for 'bulc_set_exit_assignment' including name, description, input schema, and annotations.
    {
      name: "bulc_set_exit_assignment",
      description:
        "Set the exit assignment strategy for evacuation agents. " +
        "Determines how agents choose which exit to use.",
      inputSchema: {
        type: "object" as const,
        properties: {
          mode: {
            type: "string",
            description: "Assignment mode: 'NEAREST' (closest exit), 'SHORTEST_PATH' (shortest walking path), 'BALANCED' (balance exit flow), 'CUSTOM' (manual assignment)",
            enum: ["NEAREST", "SHORTEST_PATH", "BALANCED", "CUSTOM"],
          },
          balanceThreshold: {
            type: "number",
            description: "For BALANCED mode: max agents per exit ratio difference. Default: 0.2",
          },
          customAssignments: {
            type: "array",
            description: "For CUSTOM mode: array of {agentIds: [...], exitId: '...'} assignments",
            items: {
              type: "object",
              properties: {
                agentIds: {
                  type: "array",
                  items: { type: "integer" },
                },
                exitId: {
                  type: "string",
                },
              },
            },
          },
        },
        required: ["mode"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema (SetExitAssignmentSchema) used to parse and validate tool input arguments.
    const SetExitAssignmentSchema = z.object({
      mode: z.enum(["NEAREST", "SHORTEST_PATH", "BALANCED", "CUSTOM"]),
      balanceThreshold: z.number().positive().optional(),
      customAssignments: z.array(z.object({
        agentIds: z.array(z.number().int()),
        exitId: z.string(),
      })).optional(),
    });
  • src/index.ts:139-148 (registration)
    Explicit routing in main MCP server handler dispatches 'bulc_set_exit_assignment' tool calls to the evac-specific handleEvacTool function.
    if (
      name === "bulc_set_agent_properties" ||
      name === "bulc_generate_rset_report" ||
      name === "bulc_save_evac_result" ||
      name === "bulc_set_exit_assignment" ||
      name === "bulc_set_premovement_time" ||
      name === "bulc_set_fire_coupling"
    ) {
      return await handleEvacTool(name, safeArgs);
    }
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description doesn't contradict. The description adds context about what the tool determines (exit choice behavior), but doesn't elaborate on side effects, permissions needed, or system state changes beyond what annotations already cover. It provides some behavioral insight but lacks depth for a destructive operation.

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?

Two clear, focused sentences with zero wasted words. The first sentence states the core action, and the second explains the behavioral impact. It's front-loaded and efficiently communicates the essential information without unnecessary elaboration.

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 tool with no output schema, the description adequately covers the basic purpose but lacks details about return values, error conditions, or system state changes. Given the complexity of evacuation simulation and the destructive nature, more context about consequences would be helpful, though annotations provide some safety information.

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?

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions the tool's purpose generally but doesn't clarify parameter interactions or usage examples, meeting the baseline for high schema coverage.

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 specific action ('Set the exit assignment strategy') and resource ('for evacuation agents'), with additional detail on what it determines ('how agents choose which exit to use'). It distinguishes from siblings like 'bulc_set_agent_properties' or 'bulc_set_evac_model' by focusing specifically on exit assignment logic.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether evacuation agents must exist first), nor does it differentiate from sibling tools like 'bulc_set_agent_properties' that might affect agent behavior. Usage context is implied but not explicitly stated.

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