Skip to main content
Glama
using76
by using76

bulc_generate_report

Destructive

Generate analysis reports from FDS simulation results for fire safety assessments, including ASET, RSET, and combined safety analysis with visualizations.

Instructions

Generate an analysis report from FDS simulation results. Supports ASET, RSET, and combined safety analysis reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportTypeNoReport type: 'aset', 'rset', 'combined'. Default: aset
outputPathNoOutput directory for report. Default: same as results
languageNoReport language: 'EN', 'KO', 'JP', 'CN'. Default: EN
includeGraphsNoInclude time-series graphs. Default: true
includeSlicesNoInclude slice visualizations. Default: true

Implementation Reference

  • Handler case for bulc_generate_report: validates input schema and sends generate_report command to BULC client
    case "bulc_generate_report": {
      const validated = GenerateReportSchema.parse(args);
      result = await client.sendCommand({
        action: "generate_report",
        params: validated,
      });
      break;
    }
  • Zod input validation schema for bulc_generate_report tool
    const GenerateReportSchema = z.object({
      reportType: z.enum(["aset", "rset", "combined"]).optional(),
      outputPath: z.string().optional(),
      language: z.enum(["EN", "KO", "JP", "CN"]).optional(),
      includeGraphs: z.boolean().optional(),
      includeSlices: z.boolean().optional(),
    });
  • MCP tool definition for bulc_generate_report including input schema and annotations
    {
      name: "bulc_generate_report",
      description:
        "Generate an analysis report from FDS simulation results. " +
        "Supports ASET, RSET, and combined safety analysis reports.",
      inputSchema: {
        type: "object" as const,
        properties: {
          reportType: {
            type: "string",
            description: "Report type: 'aset', 'rset', 'combined'. Default: aset",
            enum: ["aset", "rset", "combined"],
          },
          outputPath: {
            type: "string",
            description: "Output directory for report. Default: same as results",
          },
          language: {
            type: "string",
            description: "Report language: 'EN', 'KO', 'JP', 'CN'. Default: EN",
            enum: ["EN", "KO", "JP", "CN"],
          },
          includeGraphs: {
            type: "boolean",
            description: "Include time-series graphs. Default: true",
          },
          includeSlices: {
            type: "boolean",
            description: "Include slice visualizations. Default: true",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:124-132 (registration)
    Registration/dispatch: routes bulc_generate_report calls to handleResultTool in main MCP server handler
    if (
      name === "bulc_open_result_viewer" ||
      name === "bulc_list_result_datasets" ||
      name === "bulc_get_point_data" ||
      name === "bulc_run_aset_analysis" ||
      name === "bulc_generate_report"
    ) {
      return await handleResultTool(name, safeArgs);
    }
  • src/index.ts:49-49 (registration)
    Includes resultTools array (containing bulc_generate_report) in the complete allTools list provided to MCP server.setRequestHandler for ListToolsRequest
    ...resultTools,       // 5 tools: open_viewer, list_datasets, point_data, aset, report
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating this is a write operation with destructive potential. The description adds context about what gets generated (analysis reports) but doesn't elaborate on what 'destructive' means in this context (e.g., overwriting files, modifying data). No rate limits, authentication needs, or specific behavioral traits are mentioned.

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 concise - one sentence that states the core purpose and lists supported report types. No wasted words, though it could be slightly more structured by separating purpose from capabilities.

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 tool with 5 parameters, 100% schema coverage, and clear annotations, the description provides adequate context about what the tool does. However, as a destructive operation with no output schema, it could benefit from more detail about what gets created/destroyed and what the output looks like. The lack of differentiation from the sibling RSET-specific tool is a notable gap.

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?

With 100% schema description coverage, all parameters are well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions (e.g., explaining what ASET/RSET reports contain, what graphs/slices show). The baseline of 3 is appropriate when 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 verb ('generate') and resource ('analysis report from FDS simulation results'), and specifies the supported report types (ASET, RSET, combined). However, it doesn't explicitly differentiate from sibling 'bulc_generate_rset_report', which appears to be a more specific version of this tool.

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 is provided about when to use this tool versus alternatives. The description mentions three report types but doesn't explain when to choose each type or what prerequisites exist (e.g., needing simulation results first). There's no mention of the sibling 'bulc_generate_rset_report' tool.

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