The server defines 3 tools. Two are substantive codebase analysis tools with good parameter descriptions and well-structured schemas (search_codebase, outline_codebase). However, the inclusion of a trivial 'addition' demo tool (adds two numbers) in production code is problematic and signals incomplete tool lifecycle management. Descriptions are generally adequate (150-250 chars), but lack dependency hints and recovery guidance. Parameter schemas are complete and properly typed for the two real tools. Error handling is not visible in the tool definitions, no guidance on retryability, user-fixable errors, or what to do on failure. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are completely absent despite tool definitions being visible. The 'addition' tool description is in Chinese, breaking English-only assumption and adding minimal value.

• Remove the 'addition' tool from production. Move it to a separate demo/test MCP server or gate it behind a feature flag. Demo tools have no place in production tool namespaces.
• Add tool annotations: Set readOnlyHint=true for search_codebase and outline_codebase to signal they are safe read operations with no side effects.
• Document output schemas in tool definitions. For search_codebase, specify: 'Returns an array of objects with fields: filePath (string), lineNumber (number), snippet (string), score (number).' For outline_codebase: 'Returns an object with fields: path (string), definitions (array of {name, type, startLine, endLine, summary?}).'
• Add recovery hints to descriptions. search_codebase: 'If no results, try broadening the query, removing path filters, or call outline_codebase first to discover file structure.' outline_codebase: 'If the glob pattern matches no files, check that paths are relative to project root and verify glob syntax.'
• Clarify the 'limit' parameter in search_codebase. Either: (a) remove the override option and use a fixed server-configured default, or (b) document exactly when an agent should override it (e.g., 'Override only if user explicitly requests a different number of results; default 20 is tuned for most queries').
• Fix the 'title' parameter description in outline_codebase. Clarify the relationship between 'title' and 'summarize': does title=true imply summarize=true? Document separately and remove the confusing parenthetical.
• Provide multi-language support for descriptions. If the server targets non-English agents, add descriptions in their language via separate fields (description_zh, description_es, etc.) rather than mixing languages in the main description field.

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry