Skip to main content
Glama

generate_violin_chart

Read-only

Create violin charts to visualize and compare statistical data distributions across categories, enabling analysis of variations and patterns.

Instructions

Generate a violin chart to show data for statistical summaries among different categories, such as, comparing the distribution of data points across categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesData for violin chart, such as, [{ category: 'Category A', value: 10 }], when the data is grouped, the 'group' field is required, such as, [{ category: 'Category B', value: 20, group: 'Group A' }].
styleNoStyle configuration for the chart with a JSON object, optional.
themeNoSet the theme for the chart, optional, default is 'default'.default
widthNoSet the width of chart, default is 600.
heightNoSet the height of chart, default is 400.
titleNoSet the title of chart.
axisXTitleNoSet the x-axis title of chart.
axisYTitleNoSet the y-axis title of chart.

Implementation Reference

  • Generic execution handler for the generate_violin_chart tool. Maps the tool name to chart type 'violin', validates arguments against the violin schema, generates the chart URL via external API, and returns the result in MCP format.
    export async function callTool(tool: string, args: object = {}) {
      logger.info(`Calling tool: ${tool}`);
      const chartType = CHART_TYPE_MAP[tool as keyof typeof CHART_TYPE_MAP];
    
      if (!chartType) {
        logger.error(`Unknown tool: ${tool}`);
        throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${tool}.`);
      }
    
      try {
        // Validate input using Zod before sending to API.
        // Select the appropriate schema based on the chart type.
        const schema = Charts[chartType].schema;
    
        if (schema) {
          // Use safeParse instead of parse and try-catch.
          const result = z.object(schema).safeParse(args);
          if (!result.success) {
            logger.error(`Invalid parameters: ${result.error.message}`);
            throw new McpError(
              ErrorCode.InvalidParams,
              `Invalid parameters: ${result.error.message}`,
            );
          }
        }
    
        const isMapChartTool = [
          "generate_district_map",
          "generate_path_map",
          "generate_pin_map",
        ].includes(tool);
    
        if (isMapChartTool) {
          // For map charts, we use the generateMap function, and return the mcp result.
          const { metadata, ...result } = await generateMap(tool, args);
          return result;
        }
    
        const url = await generateChartUrl(chartType, args);
        logger.info(`Generated chart URL: ${url}`);
    
        return {
          content: [
            {
              type: "text",
              text: url,
            },
          ],
          _meta: {
            description:
              "This is the chart's spec and configuration, which can be renderred to corresponding chart by AntV GPT-Vis chart components.",
            spec: { type: chartType, ...args },
          },
        };
        // biome-ignore lint/suspicious/noExplicitAny: <explanation>
      } catch (error: any) {
        logger.error(
          `Failed to generate chart: ${error.message || "Unknown error"}.`,
        );
        if (error instanceof McpError) throw error;
        if (error instanceof ValidateError)
          throw new McpError(ErrorCode.InvalidParams, error.message);
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to generate chart: ${error?.message || "Unknown error."}`,
        );
      }
    }
  • Zod schema defining the input structure for generate_violin_chart, including data array with category, value, optional group, and optional style, theme, dimensions, titles.
    const data = z.object({
      category: z
        .string()
        .describe("Category of the data point, such as '分类一'."),
      value: z.number().describe("Value of the data point, such as 10."),
      group: z
        .string()
        .optional()
        .describe(
          "Optional group for the data point, used for grouping in the violin chart.",
        ),
    });
    
    const schema = {
      data: z
        .array(data)
        .describe(
          "Data for violin chart, such as, [{ category: 'Category A', value: 10 }], when the data is grouped, the 'group' field is required, such as, [{ category: 'Category B', value: 20, group: 'Group A' }].",
        )
        .nonempty({ message: "Violin chart data cannot be empty." }),
      style: z
        .object({
          backgroundColor: BackgroundColorSchema,
          palette: PaletteSchema,
          startAtZero: StartAtZeroSchema,
          texture: TextureSchema,
        })
        .optional()
        .describe(
          "Style configuration for the chart with a JSON object, optional.",
        ),
      theme: ThemeSchema,
      width: WidthSchema,
      height: HeightSchema,
      title: TitleSchema,
      axisXTitle: AxisXTitleSchema,
      axisYTitle: AxisYTitleSchema,
    };
  • src/server.ts:64-77 (registration)
    Registers the MCP tool handlers: ListTools returns all enabled chart.tools including generate_violin_chart, CallTool dispatches to callTool function.
    function setupToolHandlers(server: Server): void {
      logger.info("setting up tool handlers...");
      server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: getEnabledTools().map((chart) => chart.tool),
      }));
    
      // biome-ignore lint/suspicious/noExplicitAny: <explanation>
      server.setRequestHandler(CallToolRequestSchema, async (request: any) => {
        logger.info("calling tool", request.params.name, request.params.arguments);
    
        return await callTool(request.params.name, request.params.arguments);
      });
      logger.info("tool handlers set up");
    }
  • Defines the tool specification object for generate_violin_chart used in MCP tool listing and input schema conversion.
    const tool = {
      name: "generate_violin_chart",
      description:
        "Generate a violin chart to show data for statistical summaries among different categories, such as, comparing the distribution of data points across categories.",
      inputSchema: zodToJsonSchema(schema),
      annotations: {
        title: "Generate Violin Chart",
        readOnlyHint: true,
      },
    };
  • Chart type mapping that associates 'generate_violin_chart' tool name with internal chart type 'violin'.
      generate_violin_chart: "violin",
      generate_waterfall_chart: "waterfall",
      generate_word_cloud_chart: "word-cloud",
    } as const;
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds some behavioral context by explaining what the chart visualizes ('statistical summaries among different categories') and the grouping mechanism. However, it doesn't disclose important behavioral traits like whether this generates an image file, returns a URL, or has any rate limits. The description doesn't contradict annotations, but adds only moderate value beyond them.

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 at two sentences. The first sentence clearly states the tool's purpose, and the second provides additional context about its use case. There's no wasted language, though it could be slightly more front-loaded with more specific guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (8 parameters with nested objects, no output schema), the description is minimally adequate. It covers the basic purpose but lacks details about what the tool returns (image, URL, etc.), performance characteristics, or error conditions. With rich schema coverage but no output schema and multiple sibling alternatives, the description should provide more contextual guidance about when this specific visualization is appropriate.

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?

With 100% schema description coverage, the schema comprehensively documents all 8 parameters. The description mentions 'data for statistical summaries among different categories' and 'comparing the distribution of data points across categories,' which provides high-level context about the 'data' parameter's purpose. However, it adds minimal semantic value beyond what's already in the schema descriptions for individual parameters.

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 violin chart to show data for statistical summaries among different categories.' It specifies the verb ('generate'), resource ('violin chart'), and intended use case ('show data for statistical summaries among different categories'). However, it doesn't explicitly differentiate from sibling tools like 'generate_boxplot_chart' or 'generate_histogram_chart' which also show statistical distributions, missing full sibling differentiation.

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 minimal usage guidance. It mentions 'comparing the distribution of data points across categories' which implies when to use it, but offers no explicit guidance on when to choose this over alternatives like box plots or histograms from the sibling list. There are no exclusions, prerequisites, or named alternatives provided.

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/antvis/mcp-server-chart'

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