mcp-server

There is significant overlap between tools, particularly getExoQueryDocs and getExoQueryDocsMulti which both retrieve documentation with only a single vs. multiple files distinction, and validateAndRunExoquery and validateExoquery which appear to be identical duplicates. This creates confusion about which tool to use for documentation retrieval and query validation, as their purposes are not clearly distinct.

The naming is mixed with no clear pattern: getExoQueryDocs and getExoQueryDocsMulti use camelCase, listExoQueryDocs uses camelCase but starts with 'list', runRawSql uses camelCase, and validateAndRunExoquery and validateExoquery use camelCase but are nearly identical. While all are camelCase, the verb choices (get, list, run, validate) are inconsistent in style and some names are overly long or redundant.

With 6 tools, the count is reasonable for a server focused on ExoQuery documentation and SQL validation. However, the presence of duplicate or highly overlapping tools (e.g., two documentation retrieval tools and two validation tools) suggests the count could be optimized by merging or removing redundancies, slightly reducing appropriateness.

The tool set covers key areas for ExoQuery: documentation access (single and multi-file), listing documentation, raw SQL execution, and ExoQuery code validation/execution. However, there are minor gaps such as no tool for schema management or direct database connection handling, and the duplication in validation tools creates redundancy rather than extending coverage.