Skip to main content
Glama

create_line_based_element

Create walls, beams, or pipes in Revit by specifying start and end points, dimensions, and level information in millimeters. Supports batch creation of multiple elements.

Instructions

Create one or more line-based elements in Revit such as walls, beams, or pipes. Supports batch creation with detailed parameters including family type ID, start and end points, thickness, height, and level information. All units are in millimeters (mm).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesArray of line-based elements to create

Implementation Reference

  • Handler function that executes the tool logic by sending the input parameters to the Revit client using withRevitConnection and returns the response or error.
    async (args, extra) => {
      const params = args;
    
      try {
        const response = await withRevitConnection(async (revitClient) => {
          return await revitClient.sendCommand(
            "create_line_based_element",
            params
          );
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Create line-based element failed: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for creating line-based elements, including name, typeId, locationLine with start/end points, thickness, height, baseLevel, and baseOffset.
    {
      data: z
        .array(
          z.object({
            name: z
              .string()
              .describe("Description of the element (e.g., wall, beam)"),
            typeId: z
              .number()
              .optional()
              .describe("The ID of the family type to create."),
            locationLine: 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"),
                }),
              })
              .describe("The line defining the element's location"),
            thickness: z
              .number()
              .describe(
                "Thickness/width of the element (e.g., wall thickness)"
              ),
            height: z
              .number()
              .describe("Height of the element (e.g., wall height)"),
            baseLevel: z.number().describe("Base level height"),
            baseOffset: z.number().describe("Offset from the base level"),
          })
        )
        .describe("Array of line-based elements to create"),
    },
  • Registration of the create_line_based_element tool on the McpServer, including name, description, schema, and handler.
    export function registerCreateLineBasedElementTool(server: McpServer) {
      server.tool(
        "create_line_based_element",
        "Create one or more line-based elements in Revit such as walls, beams, or pipes. Supports batch creation with detailed parameters including family type ID, start and end points, thickness, height, and level information. All units are in millimeters (mm).",
        {
          data: z
            .array(
              z.object({
                name: z
                  .string()
                  .describe("Description of the element (e.g., wall, beam)"),
                typeId: z
                  .number()
                  .optional()
                  .describe("The ID of the family type to create."),
                locationLine: 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"),
                    }),
                  })
                  .describe("The line defining the element's location"),
                thickness: z
                  .number()
                  .describe(
                    "Thickness/width of the element (e.g., wall thickness)"
                  ),
                height: z
                  .number()
                  .describe("Height of the element (e.g., wall height)"),
                baseLevel: z.number().describe("Base level height"),
                baseOffset: z.number().describe("Offset from the base level"),
              })
            )
            .describe("Array of line-based elements to create"),
        },
        async (args, extra) => {
          const params = args;
    
          try {
            const response = await withRevitConnection(async (revitClient) => {
              return await revitClient.sendCommand(
                "create_line_based_element",
                params
              );
            });
    
            return {
              content: [
                {
                  type: "text",
                  text: JSON.stringify(response, null, 2),
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Create line-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. It mentions batch creation and units (mm), but does not address critical behavioral aspects such as whether this is a write operation (implied by 'create'), what permissions are required, whether changes are reversible, error handling, or response format. 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 core purpose and batch capability, the second lists key parameters and units. Every sentence adds value, though it could be slightly more front-loaded by emphasizing the creation action earlier. No wasted words.

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?

Given the complexity of creating multiple Revit elements, no annotations, and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., mutation effects, permissions), error handling, and what the tool returns. The high schema coverage helps, but for a creation tool in a domain like Revit, more context is needed for safe and effective use.

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 schema description coverage is 100%, so the schema already documents the single parameter ('data') and its nested properties comprehensively. The description adds minimal value beyond the schema by mentioning 'detailed parameters including family type ID, start and end points, thickness, height, and level information' and units (mm), but does not provide additional syntax or format details. 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 ('line-based elements in Revit such as walls, beams, or pipes'), distinguishing it from siblings like create_point_based_element and create_surface_based_element. It specifies the batch creation capability and domain context (Revit), making the purpose highly specific and differentiated.

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

Usage Guidelines3/5

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

The description implies usage for creating line-based elements in Revit, but does not explicitly state when to use this tool versus alternatives like create_point_based_element or create_surface_based_element. It mentions batch creation and detailed parameters, which provides some context, but lacks explicit guidance on prerequisites or exclusions.

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