Consumer Rights Wiki 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_wikiC | Search for articles in the Consumer Rights Wiki |
| get_page_contentC | Get the full content of a specific wiki page |
| get_page_infoB | Get metadata about a wiki page |
| get_recent_changesC | Get recent changes to the wiki |
| get_categoriesC | Get all categories or pages in a specific category |
| get_page_sectionsC | Get the section structure of a wiki page |
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: get_categories handles category listings, get_page_content retrieves full page text, get_page_info provides metadata, get_page_sections gives structural details, get_recent_changes shows edit history, and search_wiki performs article searches. The descriptions clearly differentiate each tool's function, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes, using snake_case uniformly throughout. This predictable naming scheme (e.g., get_page_content, search_wiki) makes the tool set easily navigable and understandable at a glance.
With 6 tools, this server is well-scoped for a wiki interface, covering essential operations like content retrieval, metadata access, structure analysis, change tracking, and search. Each tool earns its place without redundancy, avoiding both excessive complexity and insufficient functionality.
The tool set provides comprehensive read-only coverage for a wiki domain, including content, metadata, structure, history, and search. A minor gap exists in write operations (e.g., edit_page or create_page), but agents can still perform most common wiki interactions effectively with the available tools.