Skip to main content
Glama
santoshray02

CSV Editor

by santoshray02

get_server_info

Retrieve details about CSV Editor's data processing capabilities, including supported operations for manipulation, analysis, and validation of large files.

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 handler function for the 'get_server_info' tool. It is decorated with @mcp.tool for registration and returns detailed information about the server's name, version, description, capabilities across various categories, supported formats, and configuration settings like max file size and session timeout.
    @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": "1.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"))
        }
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. It states what the tool does but lacks behavioral details such as whether it's a read-only operation, what specific capabilities are returned, or any performance or permission considerations. This is inadequate 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 a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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 that there's an output schema (which likely details the returned information), the description doesn't need to explain return values. However, with no annotations and a vague purpose that doesn't differentiate from siblings, the description is minimally adequate but leaves gaps in usage and behavioral context.

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 there's no need for parameter details in the description. The description appropriately focuses on the tool's purpose without redundant parameter information, earning a high baseline score.

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 verb ('Get') and resource ('information about the CSV Editor capabilities'), making the purpose understandable. However, it doesn't explicitly differentiate from siblings like 'get_session_info' or 'health_check', which might also provide server-related information, so it falls short of a perfect score.

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. With siblings like 'get_session_info' and 'health_check' that might overlap in providing server or system information, there's no indication of when this specific tool is appropriate, leaving 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/santoshray02/csv-editor'

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