Skip to main content
Glama

color_elements

Assign distinct colors to Revit elements by category and parameter values to visualize data patterns in the current view, using gradient schemes or custom colors.

Instructions

Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNameYesThe name of the Revit category to color (e.g., 'Walls', 'Doors', 'Rooms')
parameterNameYesThe name of the parameter to use for grouping and coloring elements
useGradientNoWhether to use a gradient color scheme instead of random colors
customColorsNoOptional array of custom RGB colors to use for specific parameter values

Implementation Reference

  • The tool execution handler that connects to Revit, sends 'color_splash' command with parameters, and formats the success/error response into MCP content.
        async (args, extra) => {
          const params = args;
          try {
            const response = await withRevitConnection(async (revitClient) => {
              return await revitClient.sendCommand("color_splash", params);
            });
    
            // Format the response into a more user-friendly output
            if (response.success) {
              const coloredGroups = response.results || [];
    
              let resultText = `Successfully colored ${response.totalElements} elements across ${response.coloredGroups} groups.\n\n`;
              resultText += "Parameter Value Groups:\n";
    
              coloredGroups.forEach((group: any) => {
                const rgb = group.color;
                resultText += `- "${group.parameterValue}": ${group.count} elements colored with RGB(${rgb.r}, ${rgb.g}, ${rgb.b})\n`;
              });
    
              return {
                content: [
                  {
                    type: "text",
                    text: resultText,
                  },
                ],
              };
            } else {
              return {
                content: [
                  {
                    type: "text",
                    text: `Color operation failed: ${response.message}`,
                  },
                ],
              };
            }
          } catch (error) {
            return {
              content: [
                {
                  type: "text",
                  text: `Color operation failed: ${
                      error instanceof Error ? error.message : String(error)
                  }`,
                },
              ],
            };
          }
        }
    );
  • Input schema using Zod for validating tool arguments: categoryName (string), parameterName (string), useGradient (boolean, optional default false), customColors (array of RGB objects, optional).
    {
      categoryName: z
          .string()
          .describe("The name of the Revit category to color (e.g., 'Walls', 'Doors', 'Rooms')"),
      parameterName: z
          .string()
          .describe("The name of the parameter to use for grouping and coloring elements"),
      useGradient: z
          .boolean()
          .optional()
          .default(false)
          .describe("Whether to use a gradient color scheme instead of random colors"),
      customColors: z
          .array(
              z.object({
                r: z.number().int().min(0).max(255),
                g: z.number().int().min(0).max(255),
                b: z.number().int().min(0).max(255),
              })
          )
          .optional()
          .describe("Optional array of custom RGB colors to use for specific parameter values"),
    },
  • The registration function that calls server.tool to register the 'color_elements' tool with its name, description, input schema, and handler. This function is dynamically invoked from src/tools/register.ts.
    export function registerColorElementsTool(server: McpServer) {
      server.tool(
          "color_elements",
          "Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color.",
          {
            categoryName: z
                .string()
                .describe("The name of the Revit category to color (e.g., 'Walls', 'Doors', 'Rooms')"),
            parameterName: z
                .string()
                .describe("The name of the parameter to use for grouping and coloring elements"),
            useGradient: z
                .boolean()
                .optional()
                .default(false)
                .describe("Whether to use a gradient color scheme instead of random colors"),
            customColors: z
                .array(
                    z.object({
                      r: z.number().int().min(0).max(255),
                      g: z.number().int().min(0).max(255),
                      b: z.number().int().min(0).max(255),
                    })
                )
                .optional()
                .describe("Optional array of custom RGB colors to use for specific parameter values"),
          },
          async (args, extra) => {
            const params = args;
            try {
              const response = await withRevitConnection(async (revitClient) => {
                return await revitClient.sendCommand("color_splash", params);
              });
    
              // Format the response into a more user-friendly output
              if (response.success) {
                const coloredGroups = response.results || [];
    
                let resultText = `Successfully colored ${response.totalElements} elements across ${response.coloredGroups} groups.\n\n`;
                resultText += "Parameter Value Groups:\n";
    
                coloredGroups.forEach((group: any) => {
                  const rgb = group.color;
                  resultText += `- "${group.parameterValue}": ${group.count} elements colored with RGB(${rgb.r}, ${rgb.g}, ${rgb.b})\n`;
                });
    
                return {
                  content: [
                    {
                      type: "text",
                      text: resultText,
                    },
                  ],
                };
              } else {
                return {
                  content: [
                    {
                      type: "text",
                      text: `Color operation failed: ${response.message}`,
                    },
                  ],
                };
              }
            } catch (error) {
              return {
                content: [
                  {
                    type: "text",
                    text: `Color operation 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 full burden for behavioral disclosure. It mentions that 'Each unique parameter value gets assigned a distinct color,' which hints at output behavior, but lacks critical details: whether this is a destructive/permanent change, what happens if elements already have colors, if it requires specific permissions, or how colors are assigned (random vs. systematic). For a visual modification tool, this is insufficient.

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 concise (two sentences) and front-loaded with the core purpose. Every sentence adds value: the first defines the action, the second clarifies the coloring mechanism. No redundant or vague phrasing.

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 (visual modification tool with 4 parameters, no annotations, and no output schema), the description is incomplete. It doesn't address key contextual aspects: whether the coloring is temporary or persistent, what the visual output looks like, error conditions (e.g., invalid category/parameter), or how it integrates with sibling tools. The agent lacks sufficient guidance 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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional semantic context beyond what's in the schema (e.g., it doesn't explain how 'customColors' interacts with 'useGradient' or provide examples of parameter values). 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.

Purpose4/5

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

The description clearly states the tool's purpose: 'Color elements in the current view based on a category and parameter value.' It specifies the action (color), target (elements in current view), and grouping mechanism (category and parameter value). However, it doesn't explicitly differentiate from sibling tools like 'get_current_view_elements' or 'operate_element' which might also manipulate view elements.

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., needing an open document or view), nor does it suggest when other tools might be more appropriate (e.g., 'get_current_view_elements' for inspection first). The agent must infer usage from context 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/ideook/revit-mcp'

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