Skip to main content
Glama
santoshray02

CSV Editor

by santoshray02

disable_auto_save

Prevent automatic saving of CSV files during editing sessions to maintain manual control over file versions and prevent unintended changes.

Instructions

Disable auto-save for a session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler implementation for the 'disable_auto_save' tool. Retrieves the CSV session and invokes the session's disable_auto_save method, handling errors and logging.
    async def disable_auto_save(
        session_id: str,
        ctx: Context = None
    ) -> Dict[str, Any]:
        """
        Disable auto-save for a session.
        
        Args:
            session_id: Session identifier
            ctx: FastMCP context
            
        Returns:
            Dict with success status
        """
        try:
            manager = get_session_manager()
            session = manager.get_session(session_id)
            
            if not session:
                return OperationResult(
                    success=False,
                    message="Session not found",
                    error=f"No session with ID: {session_id}"
                ).model_dump()
            
            result = await session.disable_auto_save()
            
            if result["success"]:
                if ctx:
                    await ctx.info(f"Auto-save disabled for session {session_id}")
                
                return OperationResult(
                    success=True,
                    message="Auto-save disabled",
                    session_id=session_id
                ).model_dump()
            else:
                return OperationResult(
                    success=False,
                    message="Failed to disable auto-save",
                    error=result.get("error")
                ).model_dump()
                
        except Exception as e:
            logger.error(f"Error disabling auto-save: {str(e)}")
            if ctx:
                await ctx.error(f"Failed to disable auto-save: {str(e)}")
            return OperationResult(
                success=False,
                message="Failed to disable auto-save",
                error=str(e)
            ).model_dump()
  • Registers the 'disable_auto_save' tool with the MCP framework using the @mcp.tool decorator. This is the entry point exposed to MCP clients, delegating to the implementation in auto_save_operations.
    @mcp.tool
    async def disable_auto_save(
        session_id: str,
        ctx: Context = None
    ) -> Dict[str, Any]:
        """Disable auto-save for a session."""
        return await _disable_auto_save(session_id, ctx)
  • Core logic in CSVSession class that stops the periodic auto-save timer and disables the configuration.
    async def disable_auto_save(self) -> Dict[str, Any]:
        """Disable auto-save."""
        try:
            await self.auto_save_manager.stop_periodic_save()
            self.auto_save_config.enabled = False
            return {"success": True, "message": "Auto-save disabled"}
        except Exception as e:
            return {"success": False, "error": str(e)}
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Disable') which implies a mutation, but doesn't describe effects (e.g., whether changes are persistent, if it requires specific permissions, or what happens on session closure). For a mutation tool with zero annotation coverage, this is insufficient.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 an output schema (which handles return values) and only 1 parameter, the description is minimally adequate. However, as a mutation tool with no annotations, it should ideally mention more about behavioral aspects (e.g., reversibility, side effects) to be fully complete.

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 description doesn't mention any parameters, and schema description coverage is 0% (no descriptions in the schema). However, with only 1 parameter ('session_id'), the baseline is 4 for zero parameters, but since it's a required parameter that goes unexplained, it's scored lower. The description adds no value beyond the schema's structural information.

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 action ('Disable') and resource ('auto-save for a session'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'configure_auto_save' or 'get_auto_save_status', but the verb 'Disable' suggests a specific action within the auto-save functionality.

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 like 'configure_auto_save' or 'get_auto_save_status'. It doesn't mention prerequisites (e.g., needing an active session) or exclusions, leaving the agent to infer usage from context alone.

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