The LPC MCP Server provides four tools for code navigation and diagnostics on LPC files. All tools have descriptions (10-100 chars, all above minimum but several are brief), and input schemas are present with basic parameter descriptions. However, the descriptions lack depth regarding LLM decision-making (when to choose one tool over another, what to do with results), output schemas are not documented, and error handling is absent from the definitions. Tool names follow the get_*/find_* pattern correctly. Parameters have types and brief descriptions, but lack examples of constraints (e.g., for file paths). The tools are narrowly focused (good composition) but lack guidance on chaining behavior. Overall, the definitions are functional but suboptimal for LLM reasoning.

• Expand tool descriptions from 45 - 50 chars to 80 - 150 chars. For each tool, explicitly answer: (1) What does it return? (2) When should the LLM call it instead of another tool? (3) What should the LLM do with the result? Example for lpc_hover: 'Returns type signature, documentation, and location for the symbol at the given position in an LPC file. Use this to understand a symbol's contract before calling it or modifying it. Returns name, kind, documentation string, and file location.'
• Document all output schemas. For lpc_hover: {type: 'object', properties: {name, kind, documentation, location: {file, line, character}}}. For lpc_definition: {type: 'object', properties: {file, line, character}}. For lpc_references: {type: 'array', items: {file, line, character, context}}. For lpc_diagnostics: {type: 'object', properties: {diagnostics: array of {message, severity, line, character}}}.
• Add error-handling guidance to each tool description. Example: 'If no definition is found, the tool returns null. In this case, try lpc_references to find callers instead.' Specify which errors are transient (retry) vs permanent (user-fixable).
• Clarify parameter constraints in descriptions. For 'file': 'Absolute filesystem path to the LPC source file.' For 'line'/'character': 'Zero-indexed position within the file. line=0 is the first line, character=0 is the first character.'
• Add tool-chaining hints. In lpc_definition description: 'After finding a definition, call lpc_hover at that location to fetch documentation.' In lpc_hover description: 'After reading documentation, call lpc_references to see all uses of this symbol.'

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

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