Skip to main content
Glama
using76
by using76

bulc_export_fds

Destructive

Export FDS input files for fire simulation, including geometry and supporting files, to a specified directory for use with BULC Building Designer.

Instructions

Export the FDS input file to disk. Creates the .fds file and any required supporting files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputPathNoOutput directory path. Default: same as project file
filenameNoFDS filename (without extension). Default: project name
includeGeometryNoExport OBJ geometry file. Default: true

Implementation Reference

  • Executes the bulc_export_fds tool by parsing input arguments with ExportFdsSchema and sending an 'export_fds' command to the BULC client.
    case "bulc_export_fds": {
      const validated = ExportFdsSchema.parse(args);
      result = await client.sendCommand({
        action: "export_fds",
        params: validated,
      });
      break;
  • Zod schema for validating inputs to bulc_export_fds tool.
    const ExportFdsSchema = z.object({
      outputPath: z.string().optional(),
      filename: z.string().optional(),
      includeGeometry: z.boolean().optional(),
    });
  • Input schema definition in the tool registration object for bulc_export_fds.
    inputSchema: {
      type: "object" as const,
      properties: {
        outputPath: {
          type: "string",
          description: "Output directory path. Default: same as project file",
        },
        filename: {
          type: "string",
          description: "FDS filename (without extension). Default: project name",
        },
        includeGeometry: {
          type: "boolean",
          description: "Export OBJ geometry file. Default: true",
        },
      },
    },
  • src/index.ts:112-121 (registration)
    Routes calls to bulc_export_fds (and other FDS run tools) to the handleFdsRunTool function.
    if (
      name === "bulc_preview_fds" ||
      name === "bulc_validate_fds" ||
      name === "bulc_export_fds" ||
      name === "bulc_run_fds" ||
      name === "bulc_get_fds_status" ||
      name === "bulc_stop_fds"
    ) {
      return await handleFdsRunTool(name, safeArgs);
    }
  • src/index.ts:48-51 (registration)
    Includes fdsRunTools (containing bulc_export_fds schema) in the list of all available tools served by the MCP server.
      ...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 indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by implying file creation (a write operation). The description adds context about creating supporting files, which isn't covered by annotations, but doesn't detail potential side effects like overwriting existing files or permission requirements. No contradiction with 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 that front-load the core action ('Export the FDS input file to disk') and follow with essential details ('Creates the .fds file and any required supporting files'). Every word contributes value without redundancy or fluff.

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 no output schema and annotations covering safety (destructive), the description adequately explains what the tool does but lacks details on return values, error conditions, or integration with sibling tools. It's minimal but functional for a file export tool, fitting a moderate score.

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 the schema fully documents parameters like outputPath, filename, and includeGeometry. The description adds no additional parameter semantics beyond implying file creation, which is already covered by the tool's purpose. Baseline 3 is appropriate as the schema handles 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 action ('Export') and the resource ('FDS input file to disk'), specifying that it creates .fds and supporting files. It distinguishes from siblings like 'bulc_preview_fds' (preview vs. export) and 'bulc_get_fds_data' (retrieve vs. create files), but doesn't explicitly contrast with all siblings, keeping it at 4 rather than 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, such as 'bulc_preview_fds' for previewing or 'bulc_run_fds' for simulation. It lacks context about prerequisites (e.g., needing an FDS project loaded) or exclusions, offering only basic functional information.

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