sublime-mcp 1.8.1 → 1.8.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/fallback-tools.json +1 -1
- package/package.json +1 -1
package/fallback-tools.json
CHANGED
|
@@ -912,7 +912,7 @@
|
|
|
912
912
|
},
|
|
913
913
|
{
|
|
914
914
|
"name": "get_package_mcp_info",
|
|
915
|
-
"description": "Discover what an installed Sublime package can do, then just control it directly --\nno separate MCP server needed. Primary workflow: call this for the package name, Read\nthe files it lists under python_files to find the package's real command-dispatch table\nand settings (this tool's own commands/settings_keys are a starting point, not the full\npicture -- a package that routes many actions through one command with an 'action' arg,\nfor example, only shows up here as that one wrapper command), then call the real thing\nwith run_command or eval_python. That loop -- discover, read source, call directly -- is\nalmost always enough on its own.\nReturns: path, commands (with captions and args), settings_keys, python_files, plus\noutput_file/extension_template for the
|
|
915
|
+
"description": "Discover what an installed Sublime package can do, then just control it directly --\nno separate MCP server needed. Primary workflow: call this for the package name, Read\nthe files it lists under python_files to find the package's real command-dispatch table\nand settings (this tool's own commands/settings_keys are a starting point, not the full\npicture -- a package that routes many actions through one command with an 'action' arg,\nfor example, only shows up here as that one wrapper command), then call the real thing\nwith run_command or eval_python. That loop -- discover, read source, call directly -- is\nalmost always enough on its own.\nReturns: path, commands (with captions and args), settings_keys, python_files, plus\noutput_file/extension_template for the rare theoretical case where a standing,\nindependently-reachable MCP server is needed (e.g. a client with no eval_python-\nequivalent of its own) -- write the extension to output_file following extension_template\nand ST loads it automatically. A full audit of the real, current, popular Package Control\ncatalog (2026-09-14) found zero packages that actually needed this path -- treat it as a\ndocumented escape hatch, not something to reach for by default.",
|
|
916
916
|
"inputSchema": {
|
|
917
917
|
"type": "object",
|
|
918
918
|
"properties": {
|
package/package.json
CHANGED