No user-submitted related servers found.
Scored across 79 tools
Most tools map to a distinct resource+action, and the descriptions are unusually detailed about when to use each (e.g. assistant vs server writing engine, LanguageTool local management). However, several clusters overlap heavily: search_sources vs find_works_by_topic (both find real works), check_language vs improve_academic_style vs analyze_writing_patterns, and the six-plus audit tools (detect_ai_indicators, analyze_document_metadata, inspect_document_provenance, verify_content_credentials, audit_document_integrity, generate_ai_audit_report, final_quality_audit). An agent can tell them apart after reading, but selection among the audit/style/source-discovery families is error-prone.
The set is overwhelmingly consistent snake_case verb_noun (get_project, list_sources, create_academic_outline, validate_outline, export_document). Minor deviations exist: noun-first names like system_check and the bare ping break the verb_noun pattern. Overall highly predictable.
79 tools is far beyond a manageable surface for one server; the rubric's 50+ threshold is exceeded. Even though the domain is genuinely large (projects, documents, sources, writing, review, audits, formatting, backup), the tool count is excessive and forces an agent to navigate a huge catalog for routine tasks.
Coverage is broad and lifecycle-aware: project creation/archival, document import/extraction, source registration/verification/citation/bibliography export, outline drafting, section revision workflow, audits, formatting, and backups. Minor gaps remain (no source deletion tool, backup restore is CLI-only, no project delete/unarchive), but these are workable around.