fix: add const assertions for TypeScript literal type inference

Author: felixweinberger

src/server/mcp.test.ts

@@ -1710,17 +1710,17 @@ describe('tool()', () => {
         // Test valid tool names
         testServer.registerTool('valid-tool-name', {
             description: 'A valid tool name'
-        }, async () => ({ content: [{ type: 'text', text: 'Success' }] }));
+        }, async () => ({ content: [{ type: 'text' as const, text: 'Success' }] }));
 
         // Test tool name with warnings (starts with dash)
         testServer.registerTool('-warning-tool', {
             description: 'A tool name that generates warnings'
-        }, async () => ({ content: [{ type: 'text', text: 'Success' }] }));
+        }, async () => ({ content: [{ type: 'text' as const, text: 'Success' }] }));
 
         // Test invalid tool name (contains spaces)
         testServer.registerTool('invalid tool name', {
             description: 'An invalid tool name'
-        }, async () => ({ content: [{ type: 'text', text: 'Success' }] }));
+        }, async () => ({ content: [{ type: 'text' as const, text: 'Success' }] }));
 
         // Verify that warnings were issued (both for warnings and validation failures)
         expect(warnSpy).toHaveBeenCalled();