Skip to main content
Glama
VisActor

vchart-mcp-server

Official
by VisActor

generate_heatmap_chart

Create heatmap charts to visualize intensity patterns between two variables using Cartesian coordinates. Input data arrays to generate charts for analysis.

Instructions

Generates a heatmap chart based on a Cartesian coordinate system. It is used to visualize the intensity or density of values at the intersection of two discrete variables, suitable for revealing association patterns and distribution characteristics between variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNoChart output type. Defaults to 'image'.image
widthNoChart width. Optional, defaults to 500.
heightNoChart height. Optional, defaults to 500.
dataTableYesHeatmap data array, e.g., [{ gender: 'male', age: '20-30', size: 30 }].
transposeNo
xFieldYesDimension field. Must exist in the data.
yFieldYes
sizeFieldYesMeasure field. Must be numeric and exist in the data.
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

  • MCP CallToolRequest handler that resolves 'generate_heatmap_chart' to chartType 'heatmap', validates inputs using the tool's schema, invokes 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.'}`
        );
      }
    });
  • Zod schema defining inputs for generate_heatmap_chart: dataTable, xField/yField/sizeField, dimensions, axes configurations, theme, title, background, and colors.
    const schema = z.object({
      output: ChartOutputSchema,
      width: WidthSchema,
      height: HeightSchema,
      dataTable: z
        .array(z.any())
        .describe(
          "Heatmap data array, e.g., [{ gender: 'male', age: '20-30', size: 30 }]."
        )
        .nonempty({ message: "Heatmap data cannot be empty." }),
      transpose: z.boolean().optional(),
    
      xField: XFieldSchema,
      yField: XFieldSchema,
      sizeField: YFieldSchema,
    
      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)
    MCP ListToolsRequest handler dynamically registers all chart tools (including generate_heatmap_chart) by exposing their tool metadata from charts exports.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.values(Charts).map(chart => (chart as any).tool),
      };
    });
  • Tool metadata object defining name 'generate_heatmap_chart', description, and inputSchema (converted from Zod), exported as part of 'heatmap' for dynamic registration.
    const tool = {
      name: "generate_heatmap_chart",
      description:
        "Generates a heatmap chart based on a Cartesian coordinate system. It is used to visualize the intensity or density of values at the intersection of two discrete variables, suitable for revealing association patterns and distribution characteristics between variables.",
      inputSchema: convertZodToJsonSchema(schema),
    };
    
    export const heatmap = {
      schema,
      tool,
    };
  • Core helper function generateChartByType invoked for 'heatmap' chartType: constructs VChart specification from tool inputs, generates chart spec/image/HTML using @visactor/generate-vchart and remote server.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool does ('generates a heatmap chart') but doesn't disclose important behavioral traits such as whether it's a read-only or mutation operation, what permissions might be required, whether it has side effects, rate limits, or what the output looks like (e.g., file format, size). For a tool with 26 parameters and no output schema, 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 sized with two sentences that are front-loaded with the core purpose. The first sentence states what the tool does, and the second explains its use case. There's no wasted text, though it could be slightly more structured by explicitly separating purpose from guidelines.

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 (26 parameters, 4 required), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects or output format, nor does it provide usage guidance relative to sibling tools. For a data visualization tool with many configuration options, more context is needed to help an agent use it 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?

The schema description coverage is high at 92%, so the baseline is 3. The description adds minimal value beyond the schema by mentioning 'Cartesian coordinate system' and 'intensity or density of values,' which loosely relates to parameters like xField, yField, and sizeField, but doesn't provide additional syntax, format details, or examples beyond what's already documented in the schema properties.

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 with specific verbs ('generates a heatmap chart') and resources ('based on a Cartesian coordinate system'), and distinguishes it from siblings by specifying it's for 'visualizing intensity or density of values at the intersection of two discrete variables.' It explicitly mentions suitability for 'revealing association patterns and distribution characteristics between variables,' which differentiates it from other chart types like scatter or hierarchical charts.

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 mentions the tool is 'suitable for revealing association patterns and distribution characteristics between variables,' but doesn't explain when a heatmap is preferable over other chart types like scatter charts or dual-axis charts, nor does it mention any prerequisites or exclusions for usage.

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