io.github.Ravicha2/lit-review-council
Related Servers
Alternatives to io.github.Ravicha2/lit-review-council
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceTurn any AI agent into an academic researcher that can search, read, cite, and write full literature reviews autonomously.14MIT
- AlicenseAqualityDmaintenanceA multi-agent research system that decomposes complex queries into targeted sub-questions, searches the web in parallel, scores source credibility, and synthesizes findings into structured markdown reports.11MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP-based multi-agent retrieval-augmented generation system that enables question answering over academic papers with hybrid search, knowledge graph multi-hop reasoning, and source-cited answers.-
- AlicenseBqualityCmaintenanceA multi-step academic figure agent harness that enables AI agents to plan, generate, evaluate, and iterate publication-grade figures from sources like PMIDs, preprints, or freeform briefs.1453 PyPI1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA multimodal academic research assistant for LLM Agent papers, enabling paper search, PDF/figure understanding, knowledge graph memory, learning paths, and reproducible experiments via MCP.-

io.github.vouchdev/vouchofficial
AlicenseNot gradedqualityAmaintenanceReview-gated knowledge base for LLM agents that ensures durable memory via human-approved writes, compiling a wiki with verified citations.1 npm82MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no chance of selecting between overlapping tools. The single tool's purpose is also clearly conveyed by its name and description.
The tool name follows a clear verb_noun pattern: conduct_literature_review. With only one tool in the set, there are no naming inconsistencies to evaluate.
A single tool is on the thin side, but it functions as a high-level workflow orchestrator for the entire literature review process. The count feels borderline rather than excessive or trivially mismatched.
The tool covers the core workflow from research question and topics to a generated output bundle, so there is no dead end. Minor gaps exist around auxiliary capabilities like validating topics in advance or checking the status of past reviews, but these are workable for a one-shot orchestration tool.