Leeroopedia MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEEROOPEDIA_API_KEY | Yes | API key for Leeroopedia, required for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledgeA | Search the knowledge base for framework documentation, API references, config formats, and best practices. Covers a wide range of ML/AI frameworks, libraries, and tools with architecture docs, implementation patterns, configuration references, and troubleshooting guides. Use this tool when you need to:
IMPORTANT: Use this tool BEFORE you start coding whenever the task involves a framework or library. It is much faster and more accurate than guessing. Call this tool multiple times in parallel with different queries to search from multiple angles at once. Returns a synthesized answer with [PageID] citations. |
| build_planA | Get a structured implementation plan based on knowledge base documentation. Covers a wide range of ML/AI frameworks, libraries, and tools with architecture docs, implementation patterns, configuration references, and troubleshooting guides. Returns an actionable plan with numbered steps, specs, and validation criteria — all based on how the framework actually works. Use this tool when you:
Returns: overview, key specs, numbered steps, and validation criteria. |
| review_planA | Review your implementation plan against knowledge base documentation before coding. Pass your proposed approach and the KB will check it against documented best practices, known pitfalls, and real framework behavior — catching mistakes before you write code. Use this tool when you:
Returns: approvals (what looks good), risks, and improvement suggestions. |
| verify_code_mathA | Verify code correctness against knowledge base documentation and reference implementations. Checks your code against documented behavior, reference implementations, and API contracts — catching errors before they become bugs. Use this tool when you need:
Returns: verdict (Pass/Fail), analysis of discrepancies. |
| diagnose_failureA | Diagnose errors, failures, or unexpected behavior using knowledge base documentation. Checks your symptoms and logs against known failure patterns, common misconfigurations, and documented environment issues — finding root causes faster. Use this tool when you need:
Returns: diagnosis, fix steps, and prevention advice. |
| propose_hypothesisA | Propose ranked approaches or solutions based on knowledge base documentation. When you're unsure how to proceed, this tool suggests alternative approaches ranked by fit — all backed by documented framework patterns and best practices. Use this tool when you need:
Returns: ranked hypotheses with rationale and suggested next steps. |
| query_hyperparameter_priorsA | Query documented configuration values, recommended ranges, and tuning heuristics. Look up recommended parameter values, default settings, and tuning strategies for frameworks and libraries — based on documented best practices. Use this tool when you need:
Returns: suggestion table with ranges and KB-grounded justification. |
| get_pageA | Retrieve the full content of a specific knowledge base page by its exact ID. Other tools return [PageID] citations in their responses. If you need more detail from a cited page, call this tool with that page ID to get the full content. Use this tool when you:
Returns the page formatted as markdown, or an error if the page ID is not found. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: get_page vs search_knowledge vs query_hyperparameter_priors separate retrieval modes, and build_plan/review_plan/verify_code_math/diagnose_failure cover distinct lifecycle stages. However, propose_hypothesis overlaps noticeably with build_plan (both suggest approaches/implementation steps), and query_hyperparameter_priors can be confused with search_knowledge for config lookups.
All eight tools use consistent snake_case verb_noun patterns (query_hyperparameter_priors, search_knowledge, build_plan, review_plan, verify_code_math, diagnose_failure, propose_hypothesis). get_page is the only noun-first name but is a common idiom and still clearly readable.
Eight tools is well within the ideal 3-15 range and each maps to a distinct KB-backed capability (search, retrieve, plan, review, verify, diagnose, propose, config lookup). No tool feels redundant or padded.
The surface covers the full dev lifecycle from retrieval through planning, review, verification, and diagnosis, which matches the stated KB-assistant purpose well. A minor gap is the absence of any discovery/index tool to browse or enumerate available page IDs, leaving get_page dependent on citations from other tools.