Skip to main content
Glama
using76
by using76

bulc_set_evac_model

Destructive

Configure evacuation simulation models for building safety analysis. Set parameters for CollisionFreeSpeed, SocialForce, or GeneralizedCentrifugal models to simulate pedestrian movement during emergencies.

Instructions

Set the evacuation simulation model type and parameters. Supports CollisionFreeSpeed, SocialForce, and GeneralizedCentrifugal models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel type: 'CollisionFreeSpeed', 'SocialForce', 'GeneralizedCentrifugal'. Default: CollisionFreeSpeed
simulationTimeNoMaximum simulation time in seconds. Default: 300
timeStepNoSimulation time step in seconds. Default: 0.1
strengthNeighborRepulsionNoNeighbor repulsion strength (CollisionFreeSpeed). Default: 8.0
rangeNeighborRepulsionNoNeighbor repulsion range in meters (CollisionFreeSpeed). Default: 0.1
bodyForceNoBody force constant (SocialForce). Default: 120000
frictionNoFriction coefficient (SocialForce). Default: 240000

Implementation Reference

  • Tool registration in evacTools array, defining name, description, input schema, and annotations for the bulc_set_evac_model tool.
    {
      name: "bulc_set_evac_model",
      description:
        "Set the evacuation simulation model type and parameters. " +
        "Supports CollisionFreeSpeed, SocialForce, and GeneralizedCentrifugal models.",
      inputSchema: {
        type: "object" as const,
        properties: {
          model: {
            type: "string",
            description: "Model type: 'CollisionFreeSpeed', 'SocialForce', 'GeneralizedCentrifugal'. Default: CollisionFreeSpeed",
            enum: ["CollisionFreeSpeed", "SocialForce", "GeneralizedCentrifugal"],
          },
          simulationTime: {
            type: "number",
            description: "Maximum simulation time in seconds. Default: 300",
          },
          timeStep: {
            type: "number",
            description: "Simulation time step in seconds. Default: 0.1",
          },
          // CollisionFreeSpeed params
          strengthNeighborRepulsion: {
            type: "number",
            description: "Neighbor repulsion strength (CollisionFreeSpeed). Default: 8.0",
          },
          rangeNeighborRepulsion: {
            type: "number",
            description: "Neighbor repulsion range in meters (CollisionFreeSpeed). Default: 0.1",
          },
          // SocialForce params
          bodyForce: {
            type: "number",
            description: "Body force constant (SocialForce). Default: 120000",
          },
          friction: {
            type: "number",
            description: "Friction coefficient (SocialForce). Default: 240000",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema (SetEvacModelSchema) used in the handler to parse and validate input arguments for bulc_set_evac_model.
    const SetEvacModelSchema = z.object({
      model: z.enum(["CollisionFreeSpeed", "SocialForce", "GeneralizedCentrifugal"]).optional(),
      simulationTime: z.number().positive().optional(),
      timeStep: z.number().positive().optional(),
      strengthNeighborRepulsion: z.number().optional(),
      rangeNeighborRepulsion: z.number().optional(),
      bodyForce: z.number().optional(),
      friction: z.number().optional(),
    });
  • Handler logic within handleEvacTool switch statement: validates input using SetEvacModelSchema and forwards 'set_evac_model' action to BulcClient.
    case "bulc_set_evac_model": {
      const validated = SetEvacModelSchema.parse(args);
      result = await client.sendCommand({
        action: "set_evac_model",
        params: validated,
      });
      break;
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 aligns with by implying a configuration change ('Set'). However, it adds minimal behavioral context beyond annotations—it does not specify if this affects ongoing simulations, requires specific permissions, or has side effects like resetting other parameters. The description does not contradict annotations but offers limited extra insight.

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 action and lists the supported models. Every word contributes directly to understanding the tool's function, with no redundant or vague phrasing. It is appropriately sized for a configuration-setting tool.

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 configuration tool with no output schema, the description is minimally adequate. It covers the purpose and model options but lacks context on usage, effects, or integration with other tools (e.g., 'bulc_run_evac'). Given the annotations provide safety hints, the description meets basic needs but leaves gaps in operational guidance.

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 each parameter well-documented in the schema (e.g., defaults, units, model associations). The description only mentions the model types, which the schema already covers via the 'model' enum. It adds no meaningful semantics beyond the schema, so the baseline score of 3 is appropriate given the comprehensive schema.

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') and resource ('evacuation simulation model type and parameters'), distinguishing it from siblings like 'bulc_get_evac_settings' (which retrieves) or 'bulc_run_evac' (which executes). It explicitly lists the three supported model types, making the purpose unambiguous and distinct.

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 does not mention prerequisites (e.g., whether an evacuation simulation must be configured first), exclusions, or related tools like 'bulc_get_evac_settings' for checking current settings. Usage is implied only through the action 'Set', with no explicit 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