Skip to main content
Glama

create_surface_based_element

Create floors, ceilings, or roofs in Revit by defining boundaries, thickness, and level parameters in millimeters for batch processing.

Instructions

Create one or more surface-based elements in Revit such as floors, ceilings, or roofs. Supports batch creation with detailed parameters including family type ID, boundary lines, thickness, and level information. All units are in millimeters (mm).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesArray of surface-based elements to create

Implementation Reference

  • Handler function that processes input parameters, establishes Revit connection, sends the create_surface_based_element command, and formats the response or error.
    async (args, extra) => {
      const params = args;
      try {
        const response = await withRevitConnection(async (revitClient) => {
          return await revitClient.sendCommand(
            "create_surface_based_element",
            params
          );
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Create surface-based element failed: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the tool, including array of elements with name, typeId, boundary (with outerLoop of line segments), thickness, baseLevel, and baseOffset.
    {
      data: z
        .array(
          z.object({
            name: z
              .string()
              .describe("Description of the element (e.g., floor, ceiling)"),
            typeId: z
              .number()
              .optional()
              .describe("The ID of the family type to create."),
            boundary: z
              .object({
                outerLoop: z
                  .array(
                    z.object({
                      p0: z.object({
                        x: z.number().describe("X coordinate of start point"),
                        y: z.number().describe("Y coordinate of start point"),
                        z: z.number().describe("Z coordinate of start point"),
                      }),
                      p1: z.object({
                        x: z.number().describe("X coordinate of end point"),
                        y: z.number().describe("Y coordinate of end point"),
                        z: z.number().describe("Z coordinate of end point"),
                      }),
                    })
                  )
                  .min(3)
                  .describe("Array of line segments defining the boundary"),
              })
              .describe("Boundary definition with outer loop"),
            thickness: z.number().describe("Thickness of the element"),
            baseLevel: z.number().describe("Base level height"),
            baseOffset: z.number().describe("Offset from the base level"),
          })
        )
        .describe("Array of surface-based elements to create"),
    },
  • Registration function that sets up the MCP tool on the server with name, description, schema, and handler.
    export function registerCreateSurfaceBasedElementTool(server: McpServer) {
      server.tool(
        "create_surface_based_element",
        "Create one or more surface-based elements in Revit such as floors, ceilings, or roofs. Supports batch creation with detailed parameters including family type ID, boundary lines, thickness, and level information. All units are in millimeters (mm).",
        {
          data: z
            .array(
              z.object({
                name: z
                  .string()
                  .describe("Description of the element (e.g., floor, ceiling)"),
                typeId: z
                  .number()
                  .optional()
                  .describe("The ID of the family type to create."),
                boundary: z
                  .object({
                    outerLoop: z
                      .array(
                        z.object({
                          p0: z.object({
                            x: z.number().describe("X coordinate of start point"),
                            y: z.number().describe("Y coordinate of start point"),
                            z: z.number().describe("Z coordinate of start point"),
                          }),
                          p1: z.object({
                            x: z.number().describe("X coordinate of end point"),
                            y: z.number().describe("Y coordinate of end point"),
                            z: z.number().describe("Z coordinate of end point"),
                          }),
                        })
                      )
                      .min(3)
                      .describe("Array of line segments defining the boundary"),
                  })
                  .describe("Boundary definition with outer loop"),
                thickness: z.number().describe("Thickness of the element"),
                baseLevel: z.number().describe("Base level height"),
                baseOffset: z.number().describe("Offset from the base level"),
              })
            )
            .describe("Array of surface-based elements to create"),
        },
        async (args, extra) => {
          const params = args;
          try {
            const response = await withRevitConnection(async (revitClient) => {
              return await revitClient.sendCommand(
                "create_surface_based_element",
                params
              );
            });
    
            return {
              content: [
                {
                  type: "text",
                  text: JSON.stringify(response, null, 2),
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Create surface-based element failed: ${
                    error instanceof Error ? error.message : String(error)
                  }`,
                },
              ],
            };
          }
        }
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions batch creation and units (mm), it lacks critical information such as whether this is a destructive operation, what permissions are required, error handling, or what happens on failure. For a creation tool with zero annotation coverage, this is a significant gap.

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 efficiently structured in two sentences: the first states the purpose and scope, the second adds key details about batch support and units. Every sentence earns its place, though it could be slightly more front-loaded with critical behavioral information given the lack of annotations.

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

Completeness2/5

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

For a complex creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or important behavioral aspects like whether elements are immediately visible or require view updates. The context signals indicate high complexity (nested objects in schema) that isn't adequately addressed.

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 already documents all parameters thoroughly. The description adds minimal value by mentioning 'detailed parameters including family type ID, boundary lines, thickness, and level information' and units (mm), but doesn't provide additional syntax, constraints, or examples beyond what the schema provides. Baseline 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.

Purpose5/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 ('surface-based elements in Revit such as floors, ceilings, or roofs'), with specific examples that distinguish it from siblings like create_line_based_element or create_point_based_element. It precisely defines what the tool does beyond just restating the name.

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 like create_line_based_element or create_point_based_element. It mentions batch creation and parameters but offers no context about prerequisites, dependencies, or typical use cases in relation to sibling tools.

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/ideook/revit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server