Skip to main content
Glama

get_supported_formats

Retrieve supported file formats for data analysis and visualization in VisiData, enabling users to identify compatible data sources for processing.

Instructions

Get a list of supported file formats in VisiData.

Returns: List of supported formats and their descriptions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_supported_formats tool implementation - returns a JSON string with a dictionary of supported VisiData file formats and their descriptions. Registered with @mcp.tool() decorator.
    @mcp.tool()
    def get_supported_formats() -> str:
        """
        Get a list of supported file formats in VisiData.
        
        Returns:
            List of supported formats and their descriptions
        """
        try:
            # VisiData supported formats
            formats = {
                "csv": "Comma-separated values",
                "tsv": "Tab-separated values",
                "json": "JavaScript Object Notation",
                "jsonl": "JSON Lines",
                "xlsx": "Microsoft Excel",
                "xls": "Microsoft Excel (legacy)",
                "sqlite": "SQLite database",
                "html": "HTML tables",
                "xml": "XML files",
                "yaml": "YAML files",
                "hdf5": "HDF5 scientific data format",
                "parquet": "Apache Parquet",
                "arrow": "Apache Arrow",
                "pkl": "Python pickle files",
                "zip": "ZIP archives",
                "tar": "TAR archives",
                "gz": "Gzipped files",
                "bz2": "Bzip2 compressed files",
                "xz": "XZ compressed files"
            }
            
            result = {
                "supported_formats": formats,
                "total_formats": len(formats),
                "note": "VisiData supports many more formats through plugins and loaders"
            }
            
            return json.dumps(result, indent=2)
            
        except Exception as e:
            return f"Error getting supported formats: {str(e)}\n{traceback.format_exc()}"
  • Tool registration - the @mcp.tool() decorator registers get_supported_formats as an available MCP tool.
    @mcp.tool()
Behavior3/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 discloses the return type ('List of supported formats and their descriptions'), which is helpful, but lacks details on behavioral traits like rate limits, error handling, or whether it's a static list. It doesn't contradict annotations, but could be more informative for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is extremely concise and well-structured: two sentences that directly state the action and return value, with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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

Completeness4/5

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

Given the tool's low complexity (0 parameters, no annotations) and the presence of an output schema, the description is reasonably complete. It explains what the tool does and what it returns, which is sufficient for a simple lookup tool. However, it could benefit from more context on usage relative to siblings, slightly reducing completeness.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, which is fine here, but it doesn't compensate for any gaps since there are none. A baseline of 4 is appropriate as it's complete for a parameterless tool.

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: 'Get a list of supported file formats in VisiData.' It specifies the verb ('Get') and resource ('supported file formats'), making the action unambiguous. However, it doesn't explicitly differentiate from siblings like 'load_data' or 'convert_data', which might also involve formats, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as whether it's for reference before loading data or for validation. With siblings like 'load_data' and 'convert_data' that involve formats, this lack of differentiation leaves usage unclear.

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/moeloubani/visidata-mcp'

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