Quick-Chart
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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 |
|---|---|
| GetChartImgLinkC | To draw chart and get chart image link by parameters, and parameter grammar follows Quick Chart API (quickchart.io). |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined to generate chart images via the Quick Chart API.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'GetChartImgLink' follows a clear verb_noun pattern.
A single tool is too few for a chart generation server, as it lacks basic operations like creating different chart types, customizing parameters, or managing charts, which limits functionality and scope. This feels thin and incomplete for the domain.
The tool set is severely incomplete for chart generation, offering only one tool to get a chart image link without support for creating, updating, deleting, or customizing charts, which are essential operations in this domain. This will likely cause agent failures due to missing capabilities.