Skip to main content
Glama
VisActor

vchart-mcp-server

Official
by VisActor

generate_cartesian_chart

Create Cartesian charts to visualize data trends, comparisons, and processes using line, area, bar, waterfall, ranking bar, or funnel chart types.

Instructions

Generates Cartesian charts: line (trends over time), area (cumulative totals), bar (category comparison), waterfall (incremental changes), ranking bar (ordered categories), and funnel (visualizes stages in a process or conversion rates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNoChart output type. Defaults to 'image'.image
chartTypeYes
widthNoChart width. Optional, defaults to 500.
heightNoChart height. Optional, defaults to 500.
dataTableYesData array, e.g., [{ x: '2018', y: 99.9 }]. Cannot be empty.
transposeNoSet to true only when displaying a horizontal bar chart.
xFieldYesDimension field. Must exist in the data.
yFieldYesMeasure field. Must be numeric and exist in the data.
colorFieldNoColor grouping field. Should not duplicate the dimension field.
timeFieldNoTime field, such as year or month. The x field and time field must be different. this field is required in ranking_bar
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.
stackOrPercentNoStacking mode: 'stack' for stacked data, 'percent' for percentage stacking. Requires 'color' field.

Implementation Reference

  • Central MCP tool call handler that dispatches to the appropriate chart generator by matching tool name to chart type ('cartesian' for generate_cartesian_chart), validates input with the tool's schema, calls generateChartByType, and formats the response.
    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.'}`
        );
      }
    });
  • Generates VChart specification and renders it to image, HTML, or spec JSON based on chartType ('cartesian') and input options, used by all chart tool handlers.
    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`,
      });
    }
  • Zod schema defining input parameters for generate_cartesian_chart, including dataTable, fields (xField, yField, colorField), axes configurations, theme, title, and chartType for cartesian charts.
    const schema = z.object({
      output: ChartOutputSchema,
      chartType: z.enum([
        'area',
        'line',
        'bar',
        'waterfall',
        'ranking_bar',
        'funnel',
      ]),
      width: WidthSchema,
      height: HeightSchema,
      dataTable: z
        .array(z.record(z.string(), z.any()))
        .min(1, { message: 'Data is required.' })
        .describe("Data array, e.g., [{ x: '2018', y: 99.9 }]. Cannot be empty."),
      transpose: z
        .boolean()
        .optional()
        .describe('Set to true only when displaying a horizontal bar chart.'),
      xField: XFieldSchema,
      yField: YFieldSchema,
      colorField: ColorFieldSchema,
      timeField: z
        .string()
        .optional()
        .describe(
          'Time field, such as year or month. The x field and time field must be different. this field is required in ranking_bar'
        ),
      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,
      stackOrPercent: StackSchema,
    });
  • src/server.ts:34-38 (registration)
    Registers and lists all chart tools (including generate_cartesian_chart) by dynamically exporting tool objects from imported Charts modules.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.values(Charts).map(chart => (chart as any).tool),
      };
    });
  • Defines the tool metadata (name, description, inputSchema) and exports it alongside the schema for registration in the MCP server.
    const tool = {
      name: 'generate_cartesian_chart',
      description:
        'Generates Cartesian charts: line (trends over time), area (cumulative totals), bar (category comparison), waterfall (incremental changes), ranking bar (ordered categories), and funnel (visualizes stages in a process or conversion rates).',
      inputSchema: convertZodToJsonSchema(schema),
    };
    
    export const cartesian = {
      schema,
      tool,
    };
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 only lists chart types without explaining what the tool actually does (e.g., creates visualizations from data, returns images/specs/html), performance characteristics, error conditions, or data format requirements. The description is insufficient for a complex tool with 29 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence that efficiently lists all supported chart types. Every word serves a purpose, and there's no redundant information. It's appropriately sized for a tool where detailed parameter documentation is handled in the schema.

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 chart generation tool with 29 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool produces (images? HTML? chart specifications?), how to interpret results, error handling, or performance considerations. The high parameter count and complexity demand more contextual information than provided.

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 97%, so the schema already documents most parameters thoroughly. The description adds no parameter-specific information beyond listing chart types, which corresponds to the 'chartType' parameter's enum values. This meets the baseline expectation when schema coverage is high.

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 tool's purpose: 'Generates Cartesian charts' with specific chart types listed (line, area, bar, waterfall, ranking bar, funnel). It distinguishes from sibling tools by focusing on Cartesian charts specifically, unlike polar, hierarchical, or other chart types in the sibling list.

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 when to choose Cartesian charts over other chart types (e.g., polar, scatter, heatmap) available in sibling tools, nor does it provide any context about prerequisites or typical use cases for the listed chart types.

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