Skip to main content
Glama
using76
by using76

bulc_set_simulation_time

Destructive

Configure FDS simulation duration and time step parameters to control fire simulation runtime and computational accuracy in building design.

Instructions

Set FDS simulation time parameters. Controls simulation duration and time step settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationYesTotal simulation time in seconds. Required.
dtInitNoInitial time step in seconds. Default: auto (FDS calculates)
dtMaxNoMaximum time step in seconds. Default: auto

Implementation Reference

  • Handler logic for the 'bulc_set_simulation_time' tool. Validates input parameters using Zod's SetSimulationTimeSchema and sends a 'set_simulation_time' command with the validated params to the BULC client via getBulcClient().
    case "bulc_set_simulation_time": {
      const validated = SetSimulationTimeSchema.parse(args);
      result = await client.sendCommand({
        action: "set_simulation_time",
        params: validated,
      });
      break;
    }
  • Zod schema for validating the tool's input: required 'duration' (positive number), optional 'dtInit' and 'dtMax' (positive numbers).
    const SetSimulationTimeSchema = z.object({
      duration: z.number().positive(),
      dtInit: z.number().positive().optional(),
      dtMax: z.number().positive().optional(),
    });
  • Tool definition object including name, description, inputSchema (JSON schema), and annotations. Used for tool listing and basic validation.
    {
      name: "bulc_set_simulation_time",
      description:
        "Set FDS simulation time parameters. " +
        "Controls simulation duration and time step settings.",
      inputSchema: {
        type: "object" as const,
        properties: {
          duration: {
            type: "number",
            description: "Total simulation time in seconds. Required.",
          },
          dtInit: {
            type: "number",
            description: "Initial time step in seconds. Default: auto (FDS calculates)",
          },
          dtMax: {
            type: "number",
            description: "Maximum time step in seconds. Default: auto",
          },
        },
        required: ["duration"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:102-109 (registration)
    Registration/dispatch in main CallToolRequestSchema handler: routes calls to 'bulc_set_simulation_time' (and related simulation tools) to the handleSimulationTool function.
    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);
    }
  • src/index.ts:47-47 (registration)
    Inclusion of simulationTools array (containing the tool definition) into the allTools list provided in ListToolsRequestSchema response.
    ...simulationTools,   // 4 tools: get_settings, time, output, ambient
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, confirming this is a write operation that modifies data. The description adds value by specifying it 'controls simulation duration and time step settings', which clarifies the scope of modification. It doesn't mention side effects like validation or dependencies, but provides useful context beyond annotations.

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 two concise sentences with zero wasted words. It's front-loaded with the core purpose and efficiently explains the scope. Every sentence earns its place by adding necessary information without redundancy.

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 what the tool does but lacks information about effects, dependencies, or return values. It's minimally complete given the annotations provide safety context, but doesn't fully address the mutation's impact or integration with other simulation steps.

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 clear parameter documentation. The description adds minimal value beyond the schema, only implying that parameters relate to 'duration and time step settings'. No additional syntax, constraints, or interaction details are provided, 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.

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 resource ('FDS simulation time parameters'), specifying it controls 'simulation duration and time step settings'. This distinguishes it from siblings like 'bulc_set_evac_time' or 'bulc_set_fds_fire_source', though it doesn't explicitly mention those alternatives. The purpose is specific but could be more differentiated.

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 doesn't mention prerequisites, timing within a workflow, or exclusions. With many sibling tools for simulation settings, this lack of context leaves the agent guessing about appropriate usage scenarios.

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