Skip to main content
Glama
VisActor

vchart-mcp-server

Official
by VisActor

generate_range_column_chart

Create range column charts to visualize minimum and maximum values across categories, enabling comparison of value distributions in data analysis.

Instructions

Generate a range column chart to display the value range (such as minimum and maximum) for each category, suitable for comparing the range distribution across different categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNoChart output type. Defaults to 'image'.image
widthNoChart width. Optional, defaults to 500.
heightNoChart height. Optional, defaults to 500.
dataTableYesData for the range column chart, e.g., [{ category: 'Category 01', min: 10, max: 50 }].
xFieldYesDimension field. Must exist in the data.
yFieldYes
colorFieldNoColor grouping field. Should not duplicate the dimension field.
chartThemeNoChart theme. Optional, defaults to 'light'.
titleNoChart title text.
subTitleNoChart subtitle text.
titleOrientNoTitle position in the chart.
xAxisTypeNoX-axis type: categorical ('band') or continuous ('linear').
xAxisOrientNoX-axis position in the chart.
xAxisTitleNoX-axis title.
xAxisHasGridNoShow vertical grid lines for the X-axis.
xAxisHasLabelNoShow X-axis labels.
xAxisHasTickNoShow X-axis ticks.
yAxisTypeNoY-axis type: categorical ('band') or continuous ('linear').
yAxisOrientNoY-axis position in the chart.
yAxisTitleNoY-axis title.
yAxisHasGridNoShow horizontal grid lines for the Y-axis.
yAxisHasLabelNoShow Y-axis labels.
yAxisHasTickNoShow Y-axis ticks.
backgroundNoChart background color (hex). Optional, defaults to white.
colorsNoColor palette for chart elements.

Implementation Reference

  • The MCP CallToolRequest handler that executes the tool. It maps the tool name to the chart type ('range_column'), validates inputs using the tool's schema, calls generateChartByType, and returns the chart output (spec, image URL, or HTML).
    server.setRequestHandler(CallToolRequestSchema, async request => {
      const toolName = request.params.name;
      const chartType = Object.keys(Charts).find(
        key => (Charts as any)[key].tool.name === toolName
      );
    
      if (!chartType) {
        throw new McpError(
          ErrorCode.MethodNotFound,
          `Unknown tool: ${request.params.name}.`
        );
      }
    
      try {
        // Validate input using Zod before generating chart
        const args = request.params.arguments || {};
    
        // Select the appropriate schema based on the chart type
        const schema = Charts[chartType as keyof typeof Charts].schema;
    
        if (schema) {
          const result = schema.safeParse(args);
          if (!result.success) {
            throw new McpError(
              ErrorCode.InvalidParams,
              `Invalid parameters: ${result.error.message}`
            );
          }
        }
    
        const res = await generateChartByType(chartType, args);
    
        if (res && (res as any).spec) {
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify((res as any).spec, null, 2),
              },
            ],
          };
        }
    
        if (res && (res as any).image) {
          return {
            content: [
              {
                type: 'text',
                text: (res as any).image,
              },
            ],
          };
        }
    
        if (res && (res as any).html) {
          return {
            content: [
              {
                type: 'text',
                text: (res as any).html,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: 'Failed to generate chart',
            },
          ],
        };
      } catch (error: any) {
        if (error instanceof McpError) {
          throw error;
        }
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to generate chart: ${error?.message || 'Unknown error.'}`
        );
      }
    });
  • Input schema (Zod) specific to range column chart, requiring dataTable and two yFields (e.g., min/max).
    const schema = z.object({
      output: ChartOutputSchema,
      width: WidthSchema,
      height: HeightSchema,
    
      dataTable: z
        .array(z.any())
        .describe(
          "Data for the range column chart, e.g., [{ category: 'Category 01', min: 10, max: 50 }]."
        )
        .nonempty({ message: "Range column chart data must not be empty." }),
    
      xField: XFieldSchema,
      yField: z.array(YFieldSchema).length(2),
      colorField: ColorFieldSchema,
    
      chartTheme: ThemeSchema,
      title: TitleTextSchema,
      subTitle: TitleSubTextSchema,
      titleOrient: TitleOrientSchema,
      xAxisType: XAxisTypeSchema,
      xAxisOrient: XAxisOrientSchema,
      xAxisTitle: XAxisTitleSchema,
      xAxisHasGrid: XAxisHasGridSchema,
      xAxisHasLabel: XAxisHasLabelSchema,
      xAxisHasTick: XAxisHasTickSchema,
    
      yAxisType: YAxisTypeSchema,
      yAxisOrient: YAxisOrientSchema,
      yAxisTitle: YAxisTitleSchema,
      yAxisHasGrid: YAxisHasGridSchema,
      yAxisHasLabel: YAxisHasLabelSchema,
      yAxisHasTick: YAxisHasTickSchema,
    
      background: BackgroundSchema,
      colors: ColorsSchema,
    });
  • src/server.ts:34-38 (registration)
    Registers all chart tools (including generate_range_column_chart) for the MCP listTools request.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.values(Charts).map(chart => (chart as any).tool),
      };
    });
  • Tool metadata definition with name, description, and schema conversion for MCP registration.
    const tool = {
      name: "generate_range_column_chart",
      description:
        "Generate a range column chart to display the value range (such as minimum and maximum) for each category, suitable for comparing the range distribution across different categories.",
      inputSchema: convertZodToJsonSchema(schema),
    };
  • Helper function that generates the chart spec for type 'range_column' using @visactor/generate-vchart and renders the output based on 'output' field.
    export async function generateChartByType(chartType: string, options: any) {
      const {
        title,
        subTitle,
        titleOrient,
        xAxisType,
        xAxisOrient,
        xAxisTitle,
        xAxisHasGrid,
        xAxisHasLabel,
        xAxisHasTick,
    
        yAxisType,
        yAxisOrient,
        yAxisTitle,
        yAxisHasGrid,
        yAxisHasLabel,
        yAxisHasTick,
    
        leftYAxisTitle,
        leftYAxisHasGrid,
        leftYAxisHasLabel,
        leftYAxisHasTick,
    
        rightYAxisTitle,
        rightYAxisHasGrid,
        rightYAxisHasLabel,
        rightYAxisHasTick,
    
        angleAxisTitle,
        angleAxisHasGrid,
        angleAxisHasLabel,
        angleAxisHasTick,
        angleAxisType,
    
        radiusAxisHasGrid,
        radiusAxisHasLabel,
        radiusAxisHasTick,
        radiusAxisType,
        radiusAxisTitle,
    
        output,
        width,
        height,
        ...res
      } = options;
    
      const opts = { ...res };
      const titleObj = filterValidAttributes({
        text: title,
        subText: subTitle,
        orient: titleOrient,
      });
      const xAxisObj = filterValidAttributes({
        type: xAxisType,
        orient: xAxisOrient,
        title: xAxisTitle,
        hasGrid: xAxisHasGrid,
        hasLabel: xAxisHasLabel,
        hasTick: xAxisHasTick,
      });
      const yAxisObj = filterValidAttributes({
        type: yAxisType,
        orient: yAxisOrient,
        title: yAxisTitle,
        hasGrid: yAxisHasGrid,
        hasLabel: yAxisHasLabel,
        hasTick: yAxisHasTick,
      });
      const leftYAxisObj = filterValidAttributes({
        title: leftYAxisTitle,
        hasGrid: leftYAxisHasGrid,
        hasLabel: leftYAxisHasLabel,
        hasTick: leftYAxisHasTick,
      });
      const rightYAxisObj = filterValidAttributes({
        title: rightYAxisTitle,
        hasGrid: rightYAxisHasGrid,
        hasLabel: rightYAxisHasLabel,
        hasTick: rightYAxisHasTick,
      });
      const angleAxisObj = filterValidAttributes({
        title: angleAxisTitle,
        hasGrid: angleAxisHasGrid,
        hasLabel: angleAxisHasLabel,
        hasTick: angleAxisHasTick,
        type: angleAxisType,
      });
      const radiusAxisObj = filterValidAttributes({
        hasGrid: radiusAxisHasGrid,
        hasLabel: radiusAxisHasLabel,
        hasTick: radiusAxisHasTick,
        type: radiusAxisType,
        title: radiusAxisTitle,
      });
    
      const cell: Record<string, string> = {};
    
      [
        "xField",
        "yField",
        "colorField",
        "categoryField",
        "valueField",
        "wordField",
        "sizeField",
        "timeField",
        "sourceField",
        "targetField",
        "setsField",
        "radiusField",
      ].forEach((fieldName) => {
        if (isValid(options[fieldName])) {
          cell[fieldName.replace("Field", "")] = options[fieldName];
          delete opts[fieldName];
        }
      });
    
      opts.cell = cell;
    
      if (!isEmpty(titleObj)) {
        opts.title = titleObj;
      }
    
      const axes = [
        xAxisObj,
        yAxisObj,
        leftYAxisObj,
        rightYAxisObj,
        angleAxisObj,
        radiusAxisObj,
      ];
    
      if (axes.some((axis) => !isEmpty(axis))) {
        opts.axes = axes.filter((axis) => !isEmpty(axis));
      }
    
      const { spec } = generateChart(options.chartType ?? chartType, opts);
    
      if (!spec) {
        return null;
      }
    
      if (output === "spec") {
        if (isValid(width)) {
          spec.width = width;
        }
        if (isValid(height)) {
          spec.height = height;
        }
    
        return {
          spec: spec,
        };
      }
    
      return gentrateChartImageOrHtml(output, spec, {
        width: `${width ?? 500}px`,
        height: `${height ?? 500}px`,
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool generates without mentioning any behavioral traits such as performance characteristics, error handling, or output formats beyond the implied chart. It doesn't disclose whether this is a read-only operation, if it has side effects, rate limits, or authentication needs. For a complex tool with 25 parameters, 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 appropriately concise with two sentences that efficiently convey the tool's purpose and suitable use case. It's front-loaded with the main action and avoids unnecessary details. However, it could be slightly more structured by explicitly mentioning key parameters or output types to enhance clarity without adding bulk.

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 tool's complexity (25 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain the output (e.g., what 'image' or 'spec' means), error conditions, or how to interpret results. For a data visualization tool with many configuration options, more context on usage patterns and expected outcomes is needed to guide an AI agent effectively.

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 96%, so the schema already documents most parameters thoroughly. The description adds minimal value beyond the schema, only implying that data should include 'minimum and maximum' values without explaining parameter interactions or data structure details. With high schema coverage, the baseline is 3, and the description doesn't significantly compensate with additional semantic insights.

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: 'Generate a range column chart to display the value range (such as minimum and maximum) for each category.' It specifies the verb ('Generate') and resource ('range column chart'), and explains what the chart visualizes. However, it doesn't explicitly differentiate this tool from its siblings (e.g., generate_cartesian_chart, generate_scatter_chart) beyond mentioning 'range distribution,' which might not be sufficient for clear sibling distinction.

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 provides implied usage context by stating the chart is 'suitable for comparing the range distribution across different categories.' This gives a general idea of when to use it, but it doesn't offer explicit guidance on when to choose this tool over alternatives (e.g., vs. generate_scatter_chart for correlation analysis) or any prerequisites. No exclusions or clear alternatives are mentioned.

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/VisActor/vchart-mcp-server'

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