Vega-Lite 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 |
|---|---|
| search_docsC | Search through Vega-Lite documentation for information about charts, encodings, marks, and more |
| get_exampleB | Retrieve Vega-Lite example specifications by category or type |
| validate_specC | Validate a Vega-Lite specification and check for errors |
| get_schema_infoC | Get information about Vega-Lite schema properties and structure |
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 4 tools
Each tool has a clearly distinct purpose: get_example retrieves examples, get_schema_info provides schema details, search_docs searches documentation, and validate_spec validates specifications. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_example, get_schema_info, search_docs, validate_spec) with clear, descriptive verbs. This uniformity enhances readability and predictability across the tool set.
With 4 tools, the server is well-scoped for its purpose of supporting Vega-Lite chart development. Each tool serves a distinct, essential function (examples, schema, docs, validation), and there are no extraneous tools, making the count appropriate.
The tool set covers key aspects of Vega-Lite usage: examples, schema info, documentation search, and spec validation. A minor gap exists in lacking tools for generating or modifying specifications, but agents can work around this using the provided tools effectively.