Skip to main content
Glama
markomitranic

Data Visualization MCP Server

save_data

Store data in named tables for creating visualizations later. Save datasets to reference when generating charts and graphs with Vega-Lite syntax.

Instructions

A tool which allows you to save data to a named table for later use in visualizations. When to use this tool:

  • Use this tool when you have data that you want to visualize later. How to use this tool:

  • Provide the name of the table to save the data to (for later reference) and the data itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the table to save the data to
dataYesThe data to save

Implementation Reference

  • Handler implementation for the save_data tool: extracts name and data from arguments, stores data in global saved_data dict, returns success message.
    if name == "save_data":
        save_name = arguments["name"]
        saved_data[save_name] = arguments["data"]
        return [types.TextContent(type="text", text=f"Data saved successfully to table {save_name}")]
  • Registration of the save_data tool in list_tools() handler, including name, description, and input schema definition.
    types.Tool(
        name="save_data",
        description=SAVE_DATA_TOOL_DESCRIPTION,
        inputSchema={
            "type": "object",
            "properties": {
                "name": {"type": "string", "description": "The name of the table to save the data to"},
                "data": {
                    "type": "array",
                    "items": {"type": "object", "description": "Row of the table as a dictionary/object"},
                    "description": "The data to save",
                },
            },
            "required": ["name", "data"],
        },
    ),
  • Input schema for save_data tool: requires 'name' (string) and 'data' (array of objects).
    inputSchema={
        "type": "object",
        "properties": {
            "name": {"type": "string", "description": "The name of the table to save the data to"},
            "data": {
                "type": "array",
                "items": {"type": "object", "description": "Row of the table as a dictionary/object"},
                "description": "The data to save",
            },
        },
        "required": ["name", "data"],
    },
  • Global saved_data dictionary used by save_data handler to store named data tables; pre-populated with sample data.
    saved_data = {
        "sample_data": [
            {"name": "Alice", "age": 25, "city": "New York"},
            {"name": "Bob", "age": 30, "city": "San Francisco"},
            {"name": "Charlie", "age": 35, "city": "Los Angeles"},
        ]
    }
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 of behavioral disclosure. While it states the tool 'saves data' (implying a write operation), it lacks critical details: whether this requires specific permissions, if it overwrites existing tables, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 sized and well-structured with clear sections ('When to use this tool' and 'How to use this tool'), making it easy to scan. Every sentence contributes to understanding the tool's purpose and usage, though it could be slightly more concise by integrating the sections more fluidly.

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 has 2 parameters with full schema coverage and no output schema, the description adequately covers the basic purpose and usage. However, as a mutation tool with no annotations, it lacks details on behavioral aspects like error handling, permissions, or side effects, which are important for contextual completeness. This makes it minimally viable but with clear gaps.

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?

The schema description coverage is 100%, so the schema already documents both parameters ('name' and 'data') thoroughly. The description adds minimal value beyond the schema by restating parameter purposes in the 'How to use this tool' section. This meets the baseline of 3 when the schema does the heavy lifting, but doesn't provide additional semantic context.

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: 'save data to a named table for later use in visualizations.' It specifies the verb ('save'), resource ('data'), and intended use ('for later use in visualizations'), which is clear and actionable. However, it doesn't explicitly differentiate from its sibling 'visualize_data' beyond implying a sequential relationship.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a 'When to use this tool' section that provides clear context: 'Use this tool when you have data that you want to visualize later.' This gives explicit guidance on the tool's purpose. However, it doesn't specify when NOT to use it or mention alternatives (e.g., if there are other ways to store data), which prevents a perfect score.

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

Install Server

Other Tools

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/markomitranic/mcp-vegalite-server'

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