Skip to main content
Glama
using76
by using76

bulc_create_level

Destructive

Create new floor levels in building designs by specifying elevation, name, and floor height for multi-story structures.

Instructions

Create a new floor level. Elevation is the height from ground (Z=0) to the floor surface in centimeters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLevel name (e.g., '2층', 'Second Floor', '지하')
elevationNoFloor elevation in cm from ground. If omitted, placed above highest existing level. Use negative for basement.
floorHeightNoFloor-to-ceiling height in cm. Default: 280

Implementation Reference

  • Handler case for the bulc_create_level MCP tool. Validates input using Zod schema and forwards the create_level action to the BULC client via sendCommand.
    case "bulc_create_level": {
      const validated = CreateLevelSchema.parse(args);
      result = await client.sendCommand({
        action: "create_level",
        params: validated,
      });
      break;
    }
  • Zod validation schema for the input parameters of the bulc_create_level tool (name required, elevation and floorHeight optional).
    const CreateLevelSchema = z.object({
      name: z.string(),
      elevation: z.number().optional(),
      floorHeight: z.number().positive().optional(),
    });
  • Registration of the bulc_create_level tool in the contextTools array, including description, input schema definition, and annotations.
    {
      name: "bulc_create_level",
      description:
        "Create a new floor level. Elevation is the height from ground (Z=0) to the floor surface in centimeters.",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: {
            type: "string",
            description: "Level name (e.g., '2층', 'Second Floor', '지하')",
          },
          elevation: {
            type: "number",
            description: "Floor elevation in cm from ground. If omitted, placed above highest existing level. Use negative for basement.",
          },
          floorHeight: {
            type: "number",
            description: "Floor-to-ceiling height in cm. Default: 280",
          },
        },
        required: ["name"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:151-162 (registration)
    Main MCP tool call handler routing logic that matches bulc_create_level and delegates to the specific 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:54-57 (registration)
    MCP ListToolsRequestHandler that returns the allTools array (which includes contextTools containing bulc_create_level).
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
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 mutating operation with destructive potential. The description adds useful context about elevation semantics (height from ground in cm, negative for basements) and default placement behavior when elevation is omitted. However, it doesn't elaborate on what 'destructive' means in this context (e.g., whether existing levels are affected) or mention any permissions, rate limits, or error conditions.

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 - a single sentence that immediately states the tool's purpose and provides the most critical parameter clarification (elevation definition). Every word earns its place with zero redundancy or fluff. The structure is front-loaded with the core action.

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 creation tool with destructiveHint=true and no output schema, the description is minimally adequate. It explains what gets created and clarifies the most important parameter (elevation), but doesn't address what 'destructive' means in practice, what happens on success/failure, or what the return value might be. Given the complexity of level creation in a building model context, more behavioral context would be helpful.

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 three parameters are well-documented in the schema itself. The description adds marginal value by clarifying elevation semantics ('height from ground (Z=0) to the floor surface in centimeters') and mentioning the default placement behavior when elevation is omitted. However, it doesn't explain parameter interactions or provide examples beyond what's already in the schema descriptions.

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 ('Create') and resource ('new floor level'), making the purpose immediately understandable. It distinguishes from siblings like 'bulc_create_room' or 'bulc_create_wall' by specifying it creates floor levels rather than other building elements. However, it doesn't explicitly differentiate from 'bulc_list_levels' (which lists existing levels), though the 'create' vs 'list' distinction is implied.

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., whether a building model must exist first), when not to use it, or how it relates to sibling tools like 'bulc_list_levels' or 'bulc_set_current_level'. The agent must infer usage context from the tool name alone.

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