Skip to main content
Glama
VisActor

vchart-mcp-server

Official
by VisActor

generate_polar_chart

Create polar charts (rose, radar, pie) to visualize numerical differences across categories using radius and angle coordinates.

Instructions

Generate a polar chart (rose, radar, pie) to display numerical differences among different categories using radius and angle in polar coordinates.

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 chart, e.g., [{ category: 'Category 01', value: 10 }].
chartTypeYes
transposeNo
categoryFieldYesDimension field. Must exist in the data.
valueFieldYesMeasure field. Must be numeric and exist in the data.
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.
angleAxisTitleNoAngle axis title.
angleAxisHasGridNoShow grid lines for the angle axis.
angleAxisHasLabelNoShow angle axis labels.
angleAxisHasTickNoShow angle axis ticks.
angleAxisTypeNoAngle axis type: categorical ('band') or continuous ('linear').
radiusAxisHasGridNoShow grid lines for the radius axis.
radiusAxisHasLabelNoShow radius axis labels.
radiusAxisHasTickNoShow radius axis ticks.
radiusAxisTypeNoRadius axis type: categorical ('band') or continuous ('linear').
radiusAxisTitleNoRadius axis title.
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

  • The core handler logic for generating polar charts. Destructures options, configures polar-specific axes (angle, radius), generates VChart spec using @visactor/generate-vchart, and renders to image/html/spec based on output.
    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`,
      });
    }
  • MCP CallToolRequest handler that dispatches generate_polar_chart to chartType='polar', validates input with polar.schema, calls generateChartByType, and returns the chart output as MCP content.
    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 for input validation of generate_polar_chart tool parameters, including data, fields, chartType (rose/radar/pie), and polar-specific axis configurations.
    const schema = z.object({
      output: ChartOutputSchema,
      width: WidthSchema,
      height: HeightSchema,
      dataTable: z
        .array(z.any())
        .describe(
          "Data for the chart, e.g., [{ category: 'Category 01', value: 10 }]."
        )
        .nonempty({ message: "Data must not be empty." }),
    
      chartType: z.enum(["rose", "radar", "pie"]),
      transpose: z.boolean().optional(),
    
      categoryField: XFieldSchema,
      valueField: YFieldSchema,
      colorField: ColorFieldSchema,
    
      chartTheme: ThemeSchema,
      title: TitleTextSchema,
      subTitle: TitleSubTextSchema,
      titleOrient: TitleOrientSchema,
    
      angleAxisTitle: AngleAxisTitleSchema,
      angleAxisHasGrid: AngleAxisHasGridSchema,
      angleAxisHasLabel: AngleAxisHasLabelSchema,
      angleAxisHasTick: AngleAxisHasTickSchema,
      angleAxisType: AngleAxisTypeSchema,
    
      radiusAxisHasGrid: RadiusAxisHasGridSchema,
      radiusAxisHasLabel: RadiusAxisHasLabelSchema,
      radiusAxisHasTick: RadiusAxisHasTickSchema,
      radiusAxisType: RadiusAxisTypeSchema,
      radiusAxisTitle: RadiusAxisTitleSchema,
    
      background: BackgroundSchema,
      colors: ColorsSchema,
      stackOrPercent: StackSchema,
    });
  • Tool registration metadata: name, description, and JSON schema derived from Zod schema.
    const tool = {
      name: "generate_polar_chart",
      description:
        "Generate a polar chart (rose, radar, pie) to display numerical differences among different categories using radius and angle in polar coordinates.",
      inputSchema: convertZodToJsonSchema(schema),
    };
    
    export const polar = {
      schema,
      tool,
    };
  • src/server.ts:34-37 (registration)
    Registers generate_polar_chart in MCP tools list by including polar.tool from imported Charts.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.values(Charts).map(chart => (chart as any).tool),
      };
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 states what the tool does but doesn't mention any behavioral traits: no information about permissions needed, rate limits, whether it's a read or write operation, what happens on failure, or output characteristics. For a complex chart generation tool with 26 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 a single, efficient sentence that clearly states the tool's core function. It's appropriately sized for a chart generation tool, though it could be slightly more informative given the tool's complexity. There's no wasted verbiage, and it's front-loaded with the essential information.

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 tool with 26 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns (image, HTML, or spec), doesn't mention error conditions, and provides no guidance on how to structure data or choose between chart types. The high parameter count and lack of structured metadata mean the description should do more to help an agent use this tool correctly.

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 92%, so the schema already documents most parameters well. The description adds minimal value beyond the schema: it mentions 'radius and angle in polar coordinates' which provides context for some parameters like angleAxis and radiusAxis, but doesn't explain specific parameter relationships or usage patterns. The baseline of 3 is appropriate given the high schema coverage.

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 polar chart (rose, radar, pie) to display numerical differences among different categories using radius and angle in polar coordinates.' It specifies the verb ('generate'), resource ('polar chart'), and types of charts produced. However, it doesn't explicitly differentiate from sibling tools like 'generate_cartesian_chart' beyond mentioning polar coordinates.

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 sibling tools or suggest scenarios where polar charts are preferable to other chart types. The only contextual clue is the mention of 'polar coordinates,' which implies a specific data visualization need but lacks explicit usage instructions.

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