Skip to main content
Glama
using76
by using76

bulc_set_output_settings

Destructive

Configure FDS visualization data output settings to control slice files, 3D smoke, and device intervals for fire simulation analysis.

Instructions

Configure FDS output settings for visualization data. Controls slice files, 3D smoke, and device output intervals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sliceIntervalNoInterval for slice file output in seconds. Default: 1.0
smoke3dIntervalNoInterval for 3D smoke output in seconds. Default: 1.0
deviceIntervalNoInterval for device output in seconds. Default: 1.0
plot3dIntervalNoInterval for Plot3D output in seconds. Default: 10.0
viscosityOutputNoInclude viscosity in output. Default: false
massFluxOutputNoInclude mass flux in output. Default: false

Implementation Reference

  • Handler logic for the 'bulc_set_output_settings' tool: validates input arguments using Zod schema and sends a command to the BULC client with action 'set_output_settings'.
    case "bulc_set_output_settings": {
      const validated = SetOutputSettingsSchema.parse(args);
      result = await client.sendCommand({
        action: "set_output_settings",
        params: validated,
      });
      break;
  • MCP tool schema definition for 'bulc_set_output_settings', including input schema and annotations.
    {
      name: "bulc_set_output_settings",
      description:
        "Configure FDS output settings for visualization data. " +
        "Controls slice files, 3D smoke, and device output intervals.",
      inputSchema: {
        type: "object" as const,
        properties: {
          sliceInterval: {
            type: "number",
            description: "Interval for slice file output in seconds. Default: 1.0",
          },
          smoke3dInterval: {
            type: "number",
            description: "Interval for 3D smoke output in seconds. Default: 1.0",
          },
          deviceInterval: {
            type: "number",
            description: "Interval for device output in seconds. Default: 1.0",
          },
          plot3dInterval: {
            type: "number",
            description: "Interval for Plot3D output in seconds. Default: 10.0",
          },
          viscosityOutput: {
            type: "boolean",
            description: "Include viscosity in output. Default: false",
          },
          massFluxOutput: {
            type: "boolean",
            description: "Include mass flux in output. Default: false",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema for validating inputs to the 'bulc_set_output_settings' tool in the handler.
    const SetOutputSettingsSchema = z.object({
      sliceInterval: z.number().positive().optional(),
      smoke3dInterval: z.number().positive().optional(),
      deviceInterval: z.number().positive().optional(),
      plot3dInterval: z.number().positive().optional(),
      viscosityOutput: z.boolean().optional(),
      massFluxOutput: z.boolean().optional(),
    });
  • src/index.ts:102-109 (registration)
    Registration and routing logic in main server handler: dispatches 'bulc_set_output_settings' calls to the specific 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);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating a non-read-only, potentially destructive operation. The description adds value by specifying what gets configured (slice files, 3D smoke, device output intervals), which helps the agent understand the scope of changes. However, it doesn't disclose additional behavioral traits like side effects, permissions needed, or rate limits beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with two sentences that efficiently state the purpose and key controls. It's front-loaded with the main action ('Configure FDS output settings') and avoids unnecessary details. However, the second sentence could be slightly more structured by listing the controls more clearly.

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 (6 parameters, destructive operation) and rich schema coverage (100%), the description is adequate but incomplete. It lacks output information (no output schema provided) and doesn't cover error conditions or side effects. The annotations help, but for a destructive configuration tool, more context on impact or dependencies would improve completeness.

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 in the input schema (e.g., intervals in seconds, boolean flags). The description adds minimal value beyond the schema by naming the parameter categories (slice files, 3D smoke, device output) but doesn't explain parameter interactions or provide additional context. Baseline 3 is appropriate since the schema does the heavy lifting.

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 as 'Configure FDS output settings for visualization data' with specific resource (FDS output settings) and verb (configure). It distinguishes from siblings by focusing on output intervals for visualization, unlike tools for mesh creation or simulation control. However, it doesn't explicitly differentiate from other configuration tools like bulc_set_fds_detector or bulc_set_fds_sprinkler.

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 (e.g., needing an active simulation), exclusions (e.g., not for input settings), or suggest other tools for related tasks. The context is implied through 'visualization data' but lacks explicit usage instructions.

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