This is a linter/migration tool (mcp-ready), not an MCP server. It analyzes fixture files to detect deprecated MCP patterns. The three 'tools' are actually test fixtures extracted from sample server code, not real tool definitions. Tool 'modern' has a description but no visible schema. Tool 'legacy' has no description. Tool 'demo' has an empty schema object with no properties. None are registered via a real MCP server framework, they are inferred from fixture files.

• If this is meant to be a real MCP server, implement actual tool registration using @modelcontextprotocol/server with explicit schemas and descriptions for each tool.
• Add non-empty descriptions to 'legacy' and 'demo' tools (10 - 1024 chars, explaining what each tool does and when to use it).
• Define complete input schemas for all tools with typed properties and parameter descriptions.
• Document output schemas so LLMs know what fields to expect from each tool response.
• Clarify the purpose: if mcp-ready is a linter, not a server, remove the 'tools' section or mark fixtures as non-functional examples.

Inferred effective spec: <=2025-11-25.

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API