Skip to main content
Glama
using76
by using76

bulc_set_ambient

Destructive

Configure ambient conditions for fire simulations by setting temperature, pressure, humidity, and gas concentrations to model realistic environmental scenarios.

Instructions

Set FDS ambient conditions including temperature, pressure, and species.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
temperatureNoAmbient temperature in Celsius. Default: 20
pressureNoAmbient pressure in Pa. Default: 101325
humidityNoRelative humidity (0-100%). Default: 40
o2MassFractionNoOxygen mass fraction. Default: 0.232
co2MassFractionNoCO2 mass fraction. Default: 0.000595
gravityNoGravity vector [gx, gy, gz] in m/s². Default: [0, 0, -9.81]

Implementation Reference

  • Handler logic for the 'bulc_set_ambient' tool: validates input parameters using SetAmbientSchema and sends a 'set_ambient' command to the BULC client.
    case "bulc_set_ambient": {
      const validated = SetAmbientSchema.parse(args);
      result = await client.sendCommand({
        action: "set_ambient",
        params: validated,
      });
      break;
    }
  • Tool schema definition for 'bulc_set_ambient', including input schema with properties for temperature, pressure, humidity, etc., description, and annotations.
    {
      name: "bulc_set_ambient",
      description:
        "Set FDS ambient conditions including temperature, pressure, and species.",
      inputSchema: {
        type: "object" as const,
        properties: {
          temperature: {
            type: "number",
            description: "Ambient temperature in Celsius. Default: 20",
          },
          pressure: {
            type: "number",
            description: "Ambient pressure in Pa. Default: 101325",
          },
          humidity: {
            type: "number",
            description: "Relative humidity (0-100%). Default: 40",
          },
          o2MassFraction: {
            type: "number",
            description: "Oxygen mass fraction. Default: 0.232",
          },
          co2MassFraction: {
            type: "number",
            description: "CO2 mass fraction. Default: 0.000595",
          },
          gravity: {
            type: "array",
            description: "Gravity vector [gx, gy, gz] in m/s². Default: [0, 0, -9.81]",
            items: { type: "number" },
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema (SetAmbientSchema) used in the handler for input validation of 'bulc_set_ambient' tool parameters.
    const SetAmbientSchema = z.object({
      temperature: z.number().optional(),
      pressure: z.number().positive().optional(),
      humidity: z.number().min(0).max(100).optional(),
      o2MassFraction: z.number().min(0).max(1).optional(),
      co2MassFraction: z.number().min(0).max(1).optional(),
      gravity: z.array(z.number()).length(3).optional(),
    });
  • src/index.ts:102-109 (registration)
    Registration/dispatch logic in main server handler: routes calls to 'bulc_set_ambient' (and related simulation tools) to handleSimulationTool.
    if (
      name === "bulc_get_simulation_settings" ||
      name === "bulc_set_simulation_time" ||
      name === "bulc_set_output_settings" ||
      name === "bulc_set_ambient"
    ) {
      return await handleSimulationTool(name, safeArgs);
    }
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, covering the mutation aspect. The description adds context by specifying what gets set (ambient conditions), but doesn't detail side effects, permissions, or rate limits. No contradiction with annotations exists.

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 with no wasted words. It front-loads the core action and key parameters, making it easy to parse quickly.

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 is adequate but lacks details on behavioral impact or return values. It covers the basic purpose but doesn't fully compensate for the absence of output information or deeper usage context.

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%, so parameters are well-documented in the schema. The description lists temperature, pressure, and species, which partially maps to parameters (species implies mass fractions), but adds minimal value beyond the schema. Baseline 3 is appropriate.

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 verb ('Set') and resource ('FDS ambient conditions') with specific attributes (temperature, pressure, species). It distinguishes from siblings like 'bulc_set_fds_fire_source' or 'bulc_set_evac_time' by focusing on ambient conditions, though it doesn't explicitly contrast them.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, timing in workflow, or exclusions, leaving the agent to infer usage from context alone.

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