check_table_availability — TableSpark Restaurants MCP Tool Read-only
check_table_availability
(check table availability) is one of 8 tools on the
TableSpark Restaurants
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_table_availability from your client
- Claude Code TableSpark Restaurants check_table_availability run in your project directory
- Claude Desktop TableSpark Restaurants check_table_availability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TableSpark Restaurants check_table_availability ~/.cursor/mcp.json
- VS Code TableSpark Restaurants check_table_availability .vscode/mcp.json
- Zed TableSpark Restaurants check_table_availability ~/.config/zed/settings.json
- Windsurf TableSpark Restaurants check_table_availability ~/.codeium/windsurf/mcp_config.json
- Cline TableSpark Restaurants check_table_availability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TableSpark Restaurants check_table_availability ~/.gemini/settings.json
- Grok TableSpark Restaurants check_table_availability .mcp.json (in your project root)
- ChatGPT TableSpark Restaurants check_table_availability Settings → Connectors → Advanced → Developer mode
- Claude.ai TableSpark Restaurants check_table_availability Settings → Connectors → Add custom connector
- LangChain TableSpark Restaurants check_table_availability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http restaurants https://mcp.tablespark.uk/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.