Skip to main content
Glama
Sign In
MCP Server Chart

MCP Server Chart

Official
by antvis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_venn_chart

Read-only

Create Venn diagrams to visualize relationships between sets, showing intersections and overlaps for data analysis.

Instructions

Generate a Venn diagram to visualize the relationships between different sets, showing how they intersect and overlap, such as the commonalities and differences between various groups.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data": "<data>"
    },
    "name": "generate_venn_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData for venn chart, such as, [{ label: 'A', value: 10, sets: ['A'] }, { label: 'B', value: 20, sets: ['B'] }, { label: 'C', value: 30, sets: ['C'] }, { label: 'AB', value: 5, sets: ['A', 'B'] }].
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / style / description
      Previous value: -"Custom style configuration for the chart."New value: +"Style configuration for the chart with a JSON object, optional."
  2. First observed

TDQS

B3.2/5.0
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 doesn't contradict this (it describes generation/visualization, not data modification). However, it adds minimal behavioral context beyond annotations—it mentions what the visualization shows but doesn't describe output format (e.g., image file, URL), performance characteristics, or any limitations. With annotations covering safety, the description adds some value but not rich behavioral details.

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, well-structured sentence that efficiently communicates the core purpose. It avoids redundancy and gets straight to the point. However, it could be slightly more front-loaded with key differentiators (e.g., 'For set relationships' at the beginning).

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 tool's complexity (6 parameters with nested objects) and lack of output schema, the description is minimally adequate. It explains what the tool produces (Venn diagram visualization) but doesn't describe the output format or any behavioral nuances. With annotations covering safety and schema covering parameters, the description meets basic requirements but leaves gaps about practical usage.

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 100%, so parameters are fully documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema—it doesn't explain data structure requirements, style options, or theme choices. The baseline score of 3 is appropriate when the schema carries the full parameter documentation burden.

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 Venn diagram to visualize the relationships between different sets, showing how they intersect and overlap.' It specifies the verb ('generate'), resource ('Venn diagram'), and what it visualizes ('relationships between different sets'). However, it doesn't explicitly differentiate from sibling tools like 'generate_scatter_chart' or 'generate_pie_chart' beyond mentioning Venn diagrams specifically.

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. With 24 sibling visualization tools on the server, there's no mention of when a Venn diagram is appropriate (e.g., for set relationships) versus when to use other chart types. The description only explains what the tool does, not when to choose it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools