fispro-mcp defines 6 tools with clear, domain-specific purposes (fuzzy logic inference). All tools have descriptions (avg ~120 chars) and input schemas with types. However, schemas lack depth: most parameters are minimally described (e.g., 'chemin du fichier .fis' without format/validation hints), and output schemas are not documented. Error handling returns structured dicts with 'ok' and 'error' fields but lacks recovery guidance. Tool names are verb-driven (check_, list_, describe_, infer_, explain_) and follow single-responsibility principle. No security issues detected (read-only tools, one WRITE tool properly marked). Composition is sound, tools chain logically (list_fis → describe_fis → infer). Main gaps: parameter constraints (enums, ranges), output schema documentation, and actionable error messages.

• Document output schemas for all tools. E.g., check_environment returns {ok: bool, root: str, r_backend: {available: bool, ...}, python_engine: {...}, default_backend: str}. Use JSON Schema or TypeScript-style type hints in docstrings.
• Add enum constraints to backend parameter: backend: Literal['auto', 'r', 'python'] with description 'Inference engine: auto (R if available, else Python), r (R only), or python (pure Python).'
• Enhance parameter descriptions with format/range. E.g., 'path: str, relative or absolute path to .fis file (must end in .fis or .txt); resolved relative to configured root.' For inputs: 'inputs: list[float], one numeric value per input variable, in order declared in .fis file. E.g. [25.5, 60.0].'
• Add recovery hints to error responses. When inputs length mismatches, return hint: 'Expected N inputs (order: var1, var2, ...). Got M. Check your input array.' When file not found, suggest 'Call list_fis() to discover available systems.'
• Add limit and pagination to list_fis(). Add parameters: limit (default 100, max 1000) and offset (default 0). Return {ok, root, count, total, systems, has_more}. Document in description: 'Returns up to limit systems; use offset for pagination.'