SingleStore MCP Server

MIT License
18

check_if_file_exists

Verify the existence of a file (notebook) in the user's shared space. Provides a JSON response indicating file status, including existence and a descriptive message.

Instructions

Check if a file (notebook) exists in the user's shared space. Args: file_name: Name of the file to check (with or without .ipynb extension) Returns: JSON object with the file existence status { "exists": True/False, "message": "File exists" or "File does not exist" }

Input Schema

NameRequiredDescriptionDefault
ctxNo
file_nameYes

Input Schema (JSON Schema)

{ "$defs": { "Context": { "description": "Context object providing access to MCP capabilities.\n\nThis provides a cleaner interface to MCP's RequestContext functionality.\nIt gets injected into tool and resource functions that request it via type hints.\n\nTo use context in a tool function, add a parameter with the Context type annotation:\n\n```python\n@server.tool()\ndef my_tool(x: int, ctx: Context) -> str:\n # Log messages to the client\n ctx.info(f\"Processing {x}\")\n ctx.debug(\"Debug info\")\n ctx.warning(\"Warning message\")\n ctx.error(\"Error message\")\n\n # Report progress\n ctx.report_progress(50, 100)\n\n # Access resources\n data = ctx.read_resource(\"resource://data\")\n\n # Get request info\n request_id = ctx.request_id\n client_id = ctx.client_id\n\n return str(x)\n```\n\nThe context parameter name can be anything as long as it's annotated with Context.\nThe context is optional - tools that don't need it can omit the parameter.", "properties": {}, "title": "Context", "type": "object" } }, "properties": { "ctx": { "anyOf": [ { "$ref": "#/$defs/Context" }, { "type": "null" } ], "default": null }, "file_name": { "title": "file_name", "type": "string" } }, "required": [ "file_name" ], "title": "check_if_file_existsArguments", "type": "object" }
ID: wrvorcrwsp