Skip to main content
Glama
using76
by using76

bulc_save

Destructive

Save building design projects to files within the BULC fire simulation environment, enabling persistent storage and overwrite capabilities for architectural models.

Instructions

Save the current project to file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFile path to save to. If omitted, saves to current file (overwrites).

Implementation Reference

  • Executes the bulc_save tool by validating input with SaveSchema and sending a 'save' command to the BULC client.
    case "bulc_save": {
      const validated = SaveSchema.parse(args);
      result = await client.sendCommand({
        action: "save",
        params: validated,
      });
      break;
    }
  • Tool definition for 'bulc_save' including metadata, description, input schema, and annotations.
    {
      name: "bulc_save",
      description: "Save the current project to file.",
      inputSchema: {
        type: "object" as const,
        properties: {
          path: {
            type: "string",
            description: "File path to save to. If omitted, saves to current file (overwrites).",
          },
        },
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod validation schema for bulc_save input parameters.
    const SaveSchema = z.object({
      path: z.string().optional(),
    });
  • src/index.ts:151-162 (registration)
    Registers routing for 'bulc_save' and other context tools to the handleContextTool function.
    if (
      name === "bulc_get_spatial_context" ||
      name === "bulc_get_home_info" ||
      name === "bulc_list_levels" ||
      name === "bulc_create_level" ||
      name === "bulc_set_current_level" ||
      name === "bulc_undo" ||
      name === "bulc_redo" ||
      name === "bulc_save"
    ) {
      return await handleContextTool(name, safeArgs);
    }
  • src/index.ts:40-51 (registration)
    Includes contextTools (containing bulc_save) in the complete list of available tools for the MCP server.
    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 indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by implying overwriting ('saves to current file (overwrites)'). However, the description doesn't add significant behavioral context beyond what annotations provide, such as file format, error conditions, or confirmation requirements.

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 directly states the tool's function without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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 write operation with no output schema, the description is minimally adequate. It covers the basic action but lacks details on success/failure responses, file formats, or integration with other tools, leaving gaps in context given the tool's potential impact.

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?

The input schema has 100% description coverage, fully documenting the optional 'path' parameter. The description doesn't add any meaningful parameter semantics beyond what's in the schema, so it meets 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 ('Save') and resource ('current project to file'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'bulc_export_fds' or 'bulc_save_evac_result', which might also involve saving operations to files.

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 doesn't mention prerequisites (e.g., requires an open project), exclusions, or comparisons to other save-related tools in the sibling list.

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