Skip to main content
Glama
Sign In
MCP Server Chart

MCP Server Chart

Official
by antvis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_network_graph

Read-only

Visualize relationships between entities in network graphs to analyze connections and patterns in data like social networks.

Instructions

Generate a network graph chart to show relationships (edges) between entities (nodes), such as, relationships between people in social networks.

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_network_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData for network graph chart, such as, { nodes: [{ name: 'node1' }, { name: 'node2' }], edges: [{ source: 'node1', target: 'node2', name: 'edge1' }] }
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.

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 declare readOnlyHint=true, indicating this is a safe read operation. The description adds context about what gets generated (a chart showing relationships), which is useful beyond the annotation. However, it doesn't mention important behavioral aspects like whether this creates a file, returns an image, has rate limits, or requires specific permissions. With annotations covering safety, the description adds some value but not comprehensive behavioral context.

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 - a single sentence that gets straight to the point. It's front-loaded with the core purpose and includes a helpful example. No wasted words or unnecessary elaboration. However, it could be slightly more structured by explicitly separating purpose from example.

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 (5 parameters with nested objects) and lack of output schema, the description is minimally adequate. The annotations provide safety information, and the schema documents parameters well, but the description doesn't address what the tool returns (image data, file path, etc.) or how to interpret the output. For a chart generation tool with no output schema, more information about the result would be helpful.

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 the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions 'relationships between people in social networks' which hints at the data structure but doesn't provide additional syntax, format, or usage details for the parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 network graph chart to show relationships (edges) between entities (nodes)'. It specifies the verb ('generate'), resource ('network graph chart'), and provides an example use case ('relationships between people in social networks'). However, it doesn't explicitly differentiate from sibling tools like 'generate_flow_diagram' or 'generate_sankey_chart' which might also visualize relationships.

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 tools for different chart types, there's no indication of when a network graph is appropriate versus a flow diagram, sankey chart, or other relationship visualization tools. No exclusions, prerequisites, or alternative recommendations are mentioned.

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