Skip to main content
Glama

operate_element

Perform actions on Revit elements including selection, visibility changes, color adjustments, and deletion to modify BIM models.

Instructions

Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesParameters for operating on Revit elements with specific actions

Implementation Reference

  • Handler function that sends the 'operate_element' command with parameters to the Revit client via withRevitConnection and returns the response as text content or an error message.
    async (args, extra) => {
      const params = args;
    
      try {
        const response = await withRevitConnection(async (revitClient) => {
          return await revitClient.sendCommand(
            "operate_element",
            params
          );
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Operate elements failed: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the 'operate_element' tool: elementIds array, action string, optional transparencyValue and colorValue.
    {
      data: z
        .object({
          elementIds: z
            .array(z
              .number()
              .describe("A valid Revit element ID to operate on")
            )
            .describe("Array of Revit element IDs to perform the specified action on"),
          action: z
            .string()
            .describe("The operation to perform on elements. Valid values: Select, SelectionBox, SetColor, SetTransparency, Delete, Hide, TempHide, Isolate, Unhide, ResetIsolate, Highlight. Select enables direct element selection in the active view. SelectionBox allows selection of elements by drawing a rectangular window in the view. SetColor changes the color of elements (requires elementColor parameter). SetTransparency adjusts element transparency (requires transparencyValue parameter). Highlight is a convenience operation that sets elements to red color (internally calls SetColor with red). Delete permanently removes elements from the project. Hide makes elements invisible in the current view until explicitly shown. TempHide temporarily hides elements in the current view. Isolate displays only selected elements while hiding all others. Unhide reveals previously hidden elements. ResetIsolate restores normal visibility to the view."),
          transparencyValue: z
            .number()
            .default(50)
            .describe("Transparency value (0-100) for SetTransparency action. Higher values increase transparency."),
          colorValue: z
            .array(z.number())
            .default([255, 0, 0])
            .describe("RGB color values for SetColor action. Default is red [255,0,0].")
        })
        .describe("Parameters for operating on Revit elements with specific actions"),
    },
  • Function that registers the 'operate_element' MCP tool on the server, providing name, description, schema, and handler. This function is dynamically called by src/tools/register.ts.
    export function registerOperateElementTool(server: McpServer) {
      server.tool(
        "operate_element",
        "Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc.",
        {
          data: z
            .object({
              elementIds: z
                .array(z
                  .number()
                  .describe("A valid Revit element ID to operate on")
                )
                .describe("Array of Revit element IDs to perform the specified action on"),
              action: z
                .string()
                .describe("The operation to perform on elements. Valid values: Select, SelectionBox, SetColor, SetTransparency, Delete, Hide, TempHide, Isolate, Unhide, ResetIsolate, Highlight. Select enables direct element selection in the active view. SelectionBox allows selection of elements by drawing a rectangular window in the view. SetColor changes the color of elements (requires elementColor parameter). SetTransparency adjusts element transparency (requires transparencyValue parameter). Highlight is a convenience operation that sets elements to red color (internally calls SetColor with red). Delete permanently removes elements from the project. Hide makes elements invisible in the current view until explicitly shown. TempHide temporarily hides elements in the current view. Isolate displays only selected elements while hiding all others. Unhide reveals previously hidden elements. ResetIsolate restores normal visibility to the view."),
              transparencyValue: z
                .number()
                .default(50)
                .describe("Transparency value (0-100) for SetTransparency action. Higher values increase transparency."),
              colorValue: z
                .array(z.number())
                .default([255, 0, 0])
                .describe("RGB color values for SetColor action. Default is red [255,0,0].")
            })
            .describe("Parameters for operating on Revit elements with specific actions"),
        },
        async (args, extra) => {
          const params = args;
    
          try {
            const response = await withRevitConnection(async (revitClient) => {
              return await revitClient.sendCommand(
                "operate_element",
                params
              );
            });
    
            return {
              content: [
                {
                  type: "text",
                  text: JSON.stringify(response, null, 2),
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Operate elements failed: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
            };
          }
        }
      );
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It mentions 'delete' and 'hide' without cautioning about permanence or side effects, and gives no indication of reversibility or view-level changes. The action names imply some risk, but no explicit transparency is offered.

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 a single sentence that efficiently lists key actions and 'etc.', but it could be more structured by explicitly mentioning the 'action' parameter or grouping actions by effect (e.g., destructive vs. non-destructive).

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 multi-action tool with no output schema, the description leaves out return values, error handling, and prerequisites (e.g., view context for selection actions). The schema's action details partially compensate, but the description alone is thin and does not provide a complete context.

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 covers 100% of parameters, and the action parameter's detailed description explains each valid action and its requirements. The description itself adds no additional parameter semantics beyond listing a few action names, so baseline 3 is appropriate.

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 identifies the tool as operating on Revit elements with a list of example actions (select, selectionBox, setColor, setTransparency, delete, hide). However, it does not explicitly distinguish this tool from sibling tools like delete_element or color_elements, which overlap in functionality.

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 on when to use this tool instead of the dedicated sibling tools (delete_element, color_elements). The description lists actions but does not note which sibling tool would be more appropriate for a given operation, leaving the agent without clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.