Wizzypedia MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pagesC | Search for pages in the wiki using keywords |
| read_pageB | Fetch the raw wikitext content of a page |
| create_pageC | Create a new wiki page |
| update_pageC | Update an existing wiki page |
| get_page_historyC | Get revision history of a page |
| get_categoriesC | Get categories a page belongs to |
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
Every tool has a clearly distinct purpose with no ambiguity: create_page, read_page, update_page handle the page lifecycle, while get_categories, get_page_history, and search_pages provide specific metadata and discovery functions. There is no overlap in functionality that could cause misselection.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_page, get_categories, update_page). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 6 tools, this server is well-scoped for a wiki domain, covering core operations like CRUD for pages, search, and metadata retrieval. Each tool earns its place without feeling thin or bloated, aligning with typical server sizes of 3-15 tools.
The tool set provides complete coverage for wiki operations: create, read, update for pages (though delete is omitted, which is common in wikis to preserve history), plus search and metadata tools (categories, history). There are no obvious gaps that would cause agent failures in this domain.