get_package_details — Sparkling Tracks Tours MCP Tool Read-only
get_package_details
(get package details) is one of 15 tools on the
Sparkling Tracks Tours
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_package_details from your client
- Claude Code Sparkling Tracks Tours get_package_details run in your project directory
- Claude Desktop Sparkling Tracks Tours get_package_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sparkling Tracks Tours get_package_details ~/.cursor/mcp.json
- VS Code Sparkling Tracks Tours get_package_details .vscode/mcp.json
- Zed Sparkling Tracks Tours get_package_details ~/.config/zed/settings.json
- Windsurf Sparkling Tracks Tours get_package_details ~/.codeium/windsurf/mcp_config.json
- Cline Sparkling Tracks Tours get_package_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sparkling Tracks Tours get_package_details ~/.gemini/settings.json
- Grok Sparkling Tracks Tours get_package_details .mcp.json (in your project root)
- ChatGPT Sparkling Tracks Tours get_package_details Settings → Connectors → Advanced → Developer mode
- Claude.ai Sparkling Tracks Tours get_package_details Settings → Connectors → Add custom connector
- LangChain Sparkling Tracks Tours get_package_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.sparklingtracks.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.