Skip to main content
Glama
using76
by using76

bulc_get_simulation_settings

Read-only

Retrieve current FDS fire simulation parameters including time settings, ambient conditions, output configurations, and numerical values for building design analysis.

Instructions

Get current FDS simulation settings including time, ambient conditions, output settings, and numerical parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'bulc_get_simulation_settings' tool. Sends 'get_simulation_settings' command to the BULC client with empty params and captures the result.
    case "bulc_get_simulation_settings": {
      result = await client.sendCommand({
        action: "get_simulation_settings",
        params: {},
      });
      break;
    }
  • Tool definition and schema: name, description, empty inputSchema (no parameters required), and annotations indicating read-only.
      name: "bulc_get_simulation_settings",
      description:
        "Get current FDS simulation settings including time, ambient conditions, " +
        "output settings, and numerical parameters.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:102-109 (registration)
    Server request handler routing: dispatches calls to 'bulc_get_simulation_settings' and related 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:40-51 (registration)
    Tool registration for listing: simulationTools array (including this tool) is included in allTools, served via ListToolsRequest.
    const allTools = [
      ...contextTools,      // 8 tools: spatial context, home info, levels, undo/redo, save
      ...roomTools,         // 5 tools: create, create_polygon, list, modify, delete
      ...wallTools,         // 5 tools: create, create_rectangle, list, modify, delete
      ...furnitureTools,    // 5 tools: catalog, place, list, modify, delete
      ...fdsDataTools,      // 7 tools: get, fire_source, detector, sprinkler, hvac, thermocouple, clear
      ...meshTools,         // 5 tools: list, create, auto, modify, delete
      ...simulationTools,   // 4 tools: get_settings, time, output, ambient
      ...fdsRunTools,       // 6 tools: preview, validate, export, run, status, stop
      ...resultTools,       // 5 tools: open_viewer, list_datasets, point_data, aset, report
      ...evacTools,         // 25 tools: setup, stairs, agents, run, results, advanced features
    ];
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds context by specifying what types of settings are retrieved, which helps anticipate the return structure. However, it doesn't disclose behavioral details like whether it returns defaults or current values, error conditions, or if it requires a simulation to be loaded. With annotations covering safety, this is adequate but not rich.

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 that front-loads the purpose ('Get current FDS simulation settings') and lists key components. There is no wasted verbiage, and every word contributes to understanding the tool's scope.

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 has no parameters, annotations cover safety, and no output schema exists, the description is minimally complete. It specifies what settings are included, which helps infer the return value. However, for a read operation with potential complexity in returned data, it could benefit from more detail on output format or structure to fully compensate for the lack of output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter details, so it meets the baseline of 4 for zero-parameter tools. It appropriately focuses on what the tool retrieves rather than inputs.

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 'Get' and the resource 'FDS simulation settings', with specific examples of what settings are included (time, ambient conditions, output settings, numerical parameters). It distinguishes from siblings like 'bulc_get_fds_data' or 'bulc_get_fds_status' by focusing on configuration rather than runtime data or status. However, it doesn't explicitly contrast with these siblings, so it's not a perfect 5.

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., after setting up a simulation), exclusions (e.g., not for evac settings), or direct alternatives among siblings like 'bulc_get_evac_settings'. Usage is implied from the name but not explicitly 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