Skip to main content
Glama
using76
by using76

bulc_set_current_level

Set the active floor level for editing in building design software. New rooms and walls are automatically created on this selected level.

Instructions

Set which floor level is currently active for editing. New rooms/walls will be created on this level by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelYesLevel index to set as current (0 = ground floor, 1 = first floor, etc.)

Implementation Reference

  • Tool definition including name, description, input schema for level index, and annotations.
    {
      name: "bulc_set_current_level",
      description:
        "Set which floor level is currently active for editing. New rooms/walls will be created on this level by default.",
      inputSchema: {
        type: "object" as const,
        properties: {
          level: {
            type: "integer",
            description: "Level index to set as current (0 = ground floor, 1 = first floor, etc.)",
          },
        },
        required: ["level"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
      },
    },
  • Zod validation schema for the tool input ensuring level is a non-negative integer.
    const SetCurrentLevelSchema = z.object({
      level: z.number().int().min(0),
    });
  • Handler case that parses input with SetCurrentLevelSchema and sends 'set_current_level' action to BULC client.
    case "bulc_set_current_level": {
      const validated = SetCurrentLevelSchema.parse(args);
      result = await client.sendCommand({
        action: "set_current_level",
        params: validated,
      });
      break;
    }
  • src/index.ts:40-51 (registration)
    Registration of all tools including contextTools (which contains bulc_set_current_level) for the listTools endpoint.
    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
    ];
  • src/index.ts:150-162 (registration)
    Routing logic in CallToolRequest handler that directs bulc_set_current_level calls to handleContextTool.
    // Context tools (get_spatial_context, get_home_info, levels, undo, redo, save)
    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);
    }
Behavior3/5

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

Annotations indicate this is not read-only and not destructive, which aligns with the description's 'Set' action (a configuration change rather than data deletion). The description adds useful behavioral context about the default behavior for future room/wall creation, which isn't captured in annotations. However, it doesn't mention potential side effects, error conditions, or whether the change persists across sessions.

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 perfectly concise with two sentences that each earn their place: the first states the core action, and the second explains the important downstream consequence. There's no wasted language, and the most critical information (what the tool does) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter configuration tool with good annotations and full schema coverage, the description provides adequate context about the tool's purpose and behavioral impact. The main gap is the lack of output information (no output schema), but since this appears to be a simple setter command, the description's focus on the editing context is reasonably complete.

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, the input schema already fully documents the single 'level' parameter (integer, index meaning). The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without providing extra semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Set which floor level is currently active for editing') and the resource ('floor level'), distinguishing it from siblings like 'bulc_create_level' (creates new levels) and 'bulc_list_levels' (lists existing levels). It also explains the downstream effect ('New rooms/walls will be created on this level by default'), which adds valuable context beyond just the immediate action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: when you need to change the active editing level for subsequent operations like creating rooms or walls. However, it doesn't explicitly state when NOT to use it or mention alternatives (e.g., whether you need to create a level first using 'bulc_create_level' or list existing levels with 'bulc_list_levels').

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