Quickchart-MCP-Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_chartC | Generate a chart using QuickChart |
| download_chartC | Download a chart image to a local file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'download_chart' focuses on saving a chart image to a file, while 'generate_chart' focuses on creating the chart itself. There is no overlap or ambiguity between these operations.
Both tool names follow a consistent verb_noun pattern ('download_chart' and 'generate_chart'), using snake_case and clear action verbs. This makes them predictable and easy to understand.
With only two tools, the server feels under-scoped for a chart generation domain. It lacks essential operations like updating, deleting, or listing charts, which limits its utility and completeness.
The tool set is severely incomplete for chart generation. It covers creation and downloading but misses critical operations such as updating chart data, deleting charts, or retrieving existing charts, leaving significant gaps in the workflow.