Skip to main content
Glama
santoshray02

CSV Editor

by santoshray02

get_server_info

Retrieve information about the operations and capabilities available in the CSV Editor server.

Instructions

Get information about the CSV Editor capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler/implementation of the get_server_info tool. It is registered via the @mcp.tool decorator and returns a dictionary describing the CSV Editor server's capabilities, supported formats, and configuration.
    @mcp.tool
    async def get_server_info(ctx: Context) -> dict[str, Any]:
        """Get information about the CSV Editor capabilities."""
        if ctx:
            await ctx.info("Server information requested")
    
        return {
            "name": "CSV Editor",
            "version": "2.0.0",
            "description": "A comprehensive MCP server for CSV file operations and data analysis",
            "capabilities": {
                "data_io": [
                    "load_csv",
                    "load_csv_from_url",
                    "load_csv_from_content",
                    "export_csv",
                    "multiple_export_formats",
                ],
                "data_manipulation": [
                    "filter_rows",
                    "sort_data",
                    "select_columns",
                    "rename_columns",
                    "add_column",
                    "remove_columns",
                    "change_column_type",
                    "fill_missing_values",
                    "remove_duplicates",
                ],
                "data_analysis": [
                    "get_statistics",
                    "correlation_matrix",
                    "group_by_aggregate",
                    "value_counts",
                    "detect_outliers",
                    "profile_data",
                ],
                "data_validation": ["validate_schema", "check_data_quality", "find_anomalies"],
                "session_management": ["multi_session_support", "session_isolation", "auto_cleanup"],
            },
            "supported_formats": ["csv", "tsv", "json", "excel", "parquet", "html", "markdown"],
            "max_file_size_mb": int(os.getenv("CSV_MAX_FILE_SIZE", "1024")),
            "session_timeout_minutes": int(os.getenv("CSV_SESSION_TIMEOUT", "60")),
        }
  • Registration of get_server_info as a tool using the @mcp.tool decorator on the FastMCP instance.
    @mcp.tool
  • Server setup: FastMCP instance ('mcp') is initialized here, and the @mcp.tool decorator binds the tool.
    """Main FastMCP server for CSV Editor."""
    
    import logging
    import os
    from typing import Any
    
    from fastmcp import Context, FastMCP
    
    # Configure logging
    logging.basicConfig(
        level=logging.INFO, format="%(asctime)s - %(name)s - %(levelname)s - %(message)s"
    )
    logger = logging.getLogger(__name__)
    
    # Initialize FastMCP server
    mcp = FastMCP("CSV Editor")
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only says 'get information.' It does not disclose whether the tool is read-only, idempotent, or if it requires any setup. The behavioral traits are minimal.

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?

A single clear sentence that conveys the purpose without any wasted words. It is appropriately front-loaded and concise for the tool's simplicity.

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 has no parameters and an output schema exists (though not shown), the description is adequate. It could be more specific about what 'capabilities' includes, but it is sufficiently complete for a simple info tool.

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 no parameters, so the schema coverage is 100%. Baseline for 0 parameters is 4. The description adds no param info because none exist, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves information about CSV Editor capabilities, which is a specific verb-resource combination. It distinguishes from sibling tools that focus on data manipulation or session details.

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?

No guidance on when to use this tool versus alternatives like get_session_info or health_check. The description does not mention any prerequisites or exclusions.

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/santoshray02/csv-editor'

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