Skip to main content
Glama
using76
by using76

bulc_set_agent_properties

Destructive

Configure evacuation agent parameters like radius and speed for fire simulation in building design.

Instructions

Set default properties for evacuation agents (radius, speed, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentRadiusNoDefault agent radius in meters. Default: 0.25
desiredSpeedNoDefault desired speed in m/s. Default: 1.2
maxSpeedNoDefault max speed in m/s. Default: 1.5
minSpacingNoMinimum spacing for random placement in meters. Default: 0.5

Implementation Reference

  • Handler case in handleEvacTool function that validates tool arguments using Zod and forwards the 'set_agent_properties' command to the BULC client.
    case "bulc_set_agent_properties": {
      const validated = SetAgentPropertiesSchema.parse(args);
      result = await client.sendCommand({
        action: "set_agent_properties",
        params: validated,
      });
      break;
    }
  • Zod schema used for input validation in the tool handler.
    const SetAgentPropertiesSchema = z.object({
      agentRadius: z.number().positive().optional(),
      desiredSpeed: z.number().positive().optional(),
      maxSpeed: z.number().positive().optional(),
      minSpacing: z.number().positive().optional(),
    });
  • Tool definition object in evacTools array, including name, description, inputSchema for MCP listing, and annotations.
    {
      name: "bulc_set_agent_properties",
      description:
        "Set default properties for evacuation agents (radius, speed, etc.).",
      inputSchema: {
        type: "object" as const,
        properties: {
          agentRadius: {
            type: "number",
            description: "Default agent radius in meters. Default: 0.25",
          },
          desiredSpeed: {
            type: "number",
            description: "Default desired speed in m/s. Default: 1.2",
          },
          maxSpeed: {
            type: "number",
            description: "Default max speed in m/s. Default: 1.5",
          },
          minSpacing: {
            type: "number",
            description: "Minimum spacing for random placement in meters. Default: 0.5",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:140-148 (registration)
    Specific routing condition in main tool call handler that directs bulc_set_agent_properties calls to the evac handler.
      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 provide readOnlyHint=false and destructiveHint=true, indicating a mutable, potentially destructive operation. The description adds context by specifying these are 'default' properties, suggesting they apply to future agents. However, it doesn't clarify what 'destructive' entails (e.g., overwrites existing defaults, affects ongoing simulations). No contradiction with annotations; description supplements but lacks detail on behavioral implications.

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 ('Set default properties'), followed by illustrative examples. No wasted words; every element ('evacuation agents', 'radius, speed, etc.') contributes to understanding. Efficient and well-structured for quick comprehension.

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 destructive annotations (no output schema), the description is minimally adequate. It covers the tool's purpose and hints at scope ('default properties'), but lacks details on effects (e.g., whether changes are immediate, reversible, or simulation-dependent). For a destructive tool with rich sibling context, more completeness on impact and integration would be beneficial.

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 clearly documented (e.g., 'agentRadius' as 'Default agent radius in meters. Default: 0.25'). The description only generically references 'radius, speed, etc.', adding minimal semantic value beyond the schema. Baseline score of 3 is appropriate since the schema fully defines parameters.

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 ('Set') and target ('default properties for evacuation agents'), with specific examples of properties ('radius, speed, etc.'). It distinguishes from siblings like 'bulc_get_evac_settings' (read) and 'bulc_place_evac_agents' (placement), but doesn't explicitly contrast them. Purpose is clear but sibling differentiation is implicit.

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 explicit guidance on when to use this tool versus alternatives. The description implies it's for setting default agent properties, but doesn't mention prerequisites (e.g., whether agents must exist), timing relative to other operations, or when to use sibling tools like 'bulc_modify_evac_stair' for stair-specific settings. Usage context is assumed rather than 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