Skip to main content
Glama
using76
by using76

bulc_set_fire_coupling

Destructive

Configure fire-evacuation coupling for FDS+EVAC integration by setting visibility, temperature, and CO thresholds that affect agent behavior during building evacuation simulations.

Instructions

Configure fire-evacuation coupling for FDS+EVAC integration. Sets visibility and temperature thresholds that affect agent behavior.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoEnable fire-EVAC coupling. Default: false
visibilityThresholdNoVisibility threshold in meters. Agents avoid areas below this. Default: 5
temperatureThresholdNoTemperature threshold in Celsius. Agents avoid areas above this. Default: 60
coThresholdNoCO concentration threshold in ppm. Default: 1400
speedReductionFactorNoSpeed reduction factor in smoke (0-1). Default: 0.5
updateIntervalNoFire data update interval in seconds. Default: 1.0
fdsResultPathNoPath to FDS result files (.smv). Auto-detected if not specified.

Implementation Reference

  • Handler case for bulc_set_fire_coupling tool: validates input parameters using SetFireCouplingSchema and sends 'set_fire_coupling' command to the BULC client.
    case "bulc_set_fire_coupling": {
      const validated = SetFireCouplingSchema.parse(args);
      result = await client.sendCommand({
        action: "set_fire_coupling",
        params: validated,
      });
      break;
  • MCP tool schema definition for bulc_set_fire_coupling including input schema and annotations.
    {
      name: "bulc_set_fire_coupling",
      description:
        "Configure fire-evacuation coupling for FDS+EVAC integration. " +
        "Sets visibility and temperature thresholds that affect agent behavior.",
      inputSchema: {
        type: "object" as const,
        properties: {
          enabled: {
            type: "boolean",
            description: "Enable fire-EVAC coupling. Default: false",
          },
          visibilityThreshold: {
            type: "number",
            description: "Visibility threshold in meters. Agents avoid areas below this. Default: 5",
          },
          temperatureThreshold: {
            type: "number",
            description: "Temperature threshold in Celsius. Agents avoid areas above this. Default: 60",
          },
          coThreshold: {
            type: "number",
            description: "CO concentration threshold in ppm. Default: 1400",
          },
          speedReductionFactor: {
            type: "number",
            description: "Speed reduction factor in smoke (0-1). Default: 0.5",
          },
          updateInterval: {
            type: "number",
            description: "Fire data update interval in seconds. Default: 1.0",
          },
          fdsResultPath: {
            type: "string",
            description: "Path to FDS result files (.smv). Auto-detected if not specified.",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema for input parameters of bulc_set_fire_coupling tool.
    const SetFireCouplingSchema = z.object({
      enabled: z.boolean().optional(),
      visibilityThreshold: z.number().positive().optional(),
      temperatureThreshold: z.number().positive().optional(),
      coThreshold: z.number().positive().optional(),
      speedReductionFactor: z.number().min(0).max(1).optional(),
      updateInterval: z.number().positive().optional(),
      fdsResultPath: z.string().optional(),
    });
  • src/index.ts:140-147 (registration)
    Registration/dispatch logic in main tool handler that routes bulc_set_fire_coupling to handleEvacTool.
      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 readOnlyHint=false and destructiveHint=true, which the description doesn't explicitly address. However, it adds useful context beyond annotations: it explains that the tool sets thresholds that 'affect agent behavior,' implying a configuration change that could alter simulation outcomes. It doesn't detail the destructive nature (e.g., overwriting previous settings) or other behavioral traits like side effects or error handling, but with annotations covering the safety profile, this provides moderate additional value.

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 highly concise and front-loaded: it states the core purpose in the first clause and adds key behavioral context in the second sentence. Every word earns its place, with no redundancy or fluff, making it efficient for an agent to parse.

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 complexity (7 parameters, destructive hint, no output schema), the description is minimally adequate. It covers the basic purpose and effect on agent behavior but lacks details on usage context, prerequisites, or expected outcomes. With annotations providing safety hints and schema covering parameters, it's complete enough for basic understanding but leaves gaps for informed tool invocation.

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?

The input schema has 100% description coverage, so parameters like 'enabled' and 'visibilityThreshold' are well-documented in the schema. The description adds no specific parameter information beyond implying that thresholds influence agent avoidance. This meets the baseline of 3, as the schema carries the full burden of parameter documentation.

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 tool's purpose: 'Configure fire-evacuation coupling for FDS+EVAC integration.' It specifies the action ('Configure') and the resource ('fire-evacuation coupling'), and mentions the integration context. However, it doesn't explicitly differentiate from sibling tools like 'bulc_set_evac_model' or 'bulc_set_fds_fire_source', which might also affect agent behavior in related ways.

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 mentions that it 'affects agent behavior,' but doesn't specify prerequisites (e.g., after running FDS simulations), exclusions (e.g., not for standalone EVAC), or direct alternatives among the many sibling tools. This leaves the agent with minimal contextual cues for tool selection.

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