fix: disable todos tools

Author: paoloricciuti

packages/mcp-server/src/mcp/handlers/resources/list-sections.ts

@@ -4,6 +4,7 @@ export function list_sections(server: SvelteMcp) {
 	server.resource(
 		{
 			name: 'list-sections',
+			enabled: () => false,
 			description:
 				'The list of all the available Svelte 5 and SvelteKit documentation sections in a structured format.',
 			uri: 'svelte://list-sections',

packages/mcp-server/src/mcp/handlers/tools/get-documentation.ts

@@ -5,6 +5,7 @@ export function get_documentation(server: SvelteMcp) {
 	server.tool(
 		{
 			name: 'get-documentation',
+			enabled: () => false,
 			description:
 				'Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "docs/svelte/state.md"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list_sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on.',
 			schema: v.object({

packages/mcp-server/src/mcp/handlers/tools/list-sections.ts

@@ -4,6 +4,7 @@ export function list_sections(server: SvelteMcp) {
 	server.tool(
 		{
 			name: 'list-sections',
+			enabled: () => false,
 			description:
 				'Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Returns sections as a list of "* title: [section_title], path: [file_path]" - you can use either the title or path when querying a specific section via the get_documentation tool. Always run list_sections first for any query related to Svelte development to discover available content.',
 		},