LearnOneTech MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| site_infoA | Get basic information about LearnOneTech and its public WordPress API. |
| search_articlesB | Search LearnOneTech articles by keyword. Returns titles, excerpts, dates and URLs. |
| list_articlesB | List recent LearnOneTech articles with pagination. |
| get_articleA | Retrieve a LearnOneTech article by numeric WordPress post ID or exact slug. Returns cleaned readable text plus the canonical URL. |
| list_categoriesC | List LearnOneTech WordPress article categories. |
| search_siteA | Search LearnOneTech posts and pages using WordPress's public search endpoint. |
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 6 tools
Most tools are clearly distinct, but search_articles and search_site overlap significantly since search_site also searches posts (articles) in addition to pages. The descriptions help clarify the difference, but an agent could still be uncertain which search tool to use.
Five tools follow a clear verb_noun pattern: search_articles, list_articles, get_article, list_categories, search_site. site_info breaks the pattern by using noun_noun instead of get_site_info or similar, creating a minor inconsistency.
Six tools is a well-scoped count for a content retrieval server. Each tool covers a distinct aspect of browsing and searching the public WordPress API without unnecessary bloat.
The core read-only article workflow is well covered: listing, searching, retrieving, and browsing categories. The main gap is that search_site can return pages but there is no get_page tool to retrieve a page's content, which is a minor dead end.