Skip to main content
Glama
0PValencia

@0pvalencia/chart-from-data-mcp

Official
by 0PValencia
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

@0pvalencia/chart-from-data-mcp

MCP de gráficos (bar/line/pie) vía QuickChart → PNG.

Cursor / Claude / VS Code

Local (recomendado si clonas el repo)

{
  "mcpServers": {
    "chart-from-data": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/chart-from-data-mcp/dist/cli.js"]
    }
  }
}

Tras clonar: npm install && npm run build.

npx (sin clonar)

{
  "mcpServers": {
    "chart-from-data": {
      "command": "npx",
      "args": ["-y", "@0pvalencia/chart-from-data-mcp"]
    }
  }
}

Si abres este repo en Cursor y usas npx, hace falta npm install && npm run build para que el bin local exista. Sin eso, npx falla con chart-from-data-mcp: not found y el MCP se queda cargando.

Related MCP server: mcp-plots

Install / run

npx -y @0pvalencia/chart-from-data-mcp

Local

npm install
npm run build
npm start

Tools

  • render_chart — { type, labels, values, title? } → path PNG

Usa QuickChart.

License

MIT

Available Tools

1 tool
render_chartRenderizar gráficoC

labels[] + values[] → PNG vía QuickChart.

ParametersJSON Schema
NameRequiredDescriptionDefault
typeNobar
titleNo
labelsYes
valuesYes
outputPathNo

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions QuickChart, implying an external API call, but does not disclose whether a file is written via outputPath, whether data is sent externally, or any side effects. This lack of transparency 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact formula, which is concise and free of fluff. However, it is under-specified and lacks structured sentences, trading necessary detail for brevity. It is not enough to serve as a standalone guide.

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

Completeness1/5

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

With 5 parameters, no annotations, no output schema, and an external service dependency, the description is far too sparse. It omits critical context about file output, chart type selection, and external data handling, making it inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only references labels and values. It does not explain the type enum, title, or outputPath parameters. The description adds minimal meaning beyond the raw schema, failing to compensate for the lack of parameter documentation.

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 'labels[] + values[] → PNG vía QuickChart' clearly indicates that the tool takes label and value arrays and produces a PNG via QuickChart. The verb 'render' in the tool name reinforces this. With no sibling tools, it lacks differentiation, but the purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention intended use cases, prerequisites, or exclusions. It provides only the mechanism, not the contextual rationale.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.1
    • First observedrender_chart
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.7/5.0
Disambiguation5/5

Since there is only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly described as rendering a chart from labels and values.

Naming Consistency5/5

The tool name follows a clear verb_noun pattern and is descriptive of its function. With a single tool, there is no inconsistency to evaluate.

Tool Count2/5

The server provides only one tool, which feels too thin for a chart-rendering service. Typically, such a server would include multiple tools for different chart types or configuration options.

Completeness2/5

The tool only accepts labels and values, with no ability to specify chart type, title, or other customization options. This leaves significant gaps for users who need different chart formats or styling.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • mcp-plots

    MR901
    A
    license
    A
    quality
    D
    maintenance
    A MCP server for data visualization. It exposes tools to render charts (line, bar, pie, scatter, heatmap, etc.) from data and returns plots as either image/text/mermaid diagram.
    2
    4
    MIT

  • vvk-charts-mcp

    valderan
    A
    license
    A
    quality
    D
    maintenance
    A modern Python MCP server for rendering customizable charts (line, bar, pie, scatter, area, combined dashboards) with Plotly, supporting export to PNG, SVG, and base64, and terminal charts with ANSI output.
    9
    1
    MIT

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/0PValencia/chart-from-data-mcp'

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