MCP server for handling guidelines, project rules and controlled development
This server has 29 tools with mixed quality. Naming is mostly consistent (verb_noun pattern like 'guide_get_*', 'guide_create_*'), but many tool descriptions are generic or missing critical context. Parameter schemas are present but often lack detailed constraints. Output schemas are not documented. Several tools exhibit design duplication (e.g., guide_categories, guide_collections, guide_documents vs. their direct counterparts), and error handling guidance is absent. The server prioritizes breadth over depth, a common anti-pattern that increases cognitive load on agents without improving capability.
Add a new custom category to the project configuration. Use when user explicitly requests creating a new category for organizing documentation. This operation modifies the project configuration.
Add a new collection to group related categories. Use when user explicitly requests creating a new collection for organizing categories. This operation modifies the project configuration.
JSON-based category management tool using factory pattern
JSON-based collection management tool using factory pattern
JSON-based config management tool using factory pattern
JSON-based content management tool using factory pattern
Create a new document in MCP storage
Factory-pattern tools (guide_categories, guide_collections, guide_documents, guide_content, guide_config) use a single 'action' parameter to dispatch multiple operations. This violates the single-responsibility pattern and makes LLM tool selection ambiguous, should it call guide_categories or guide_documents? The action string is opaque (e.g., 'action: get|list|create|update|delete') with no validation or constraint documentation, inviting invalid calls and confusion.
Parameter schemas lack detailed constraints. 'action' parameters (guide_categories, etc.) have no enum or validation constraint documented. Config parameters accept 'any' type with no format guidance. Parameters like 'config_key' and 'value' in guide_set_project_config lack descriptions of valid values, ranges, or formats, increasing risk of invalid input from LLMs.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 49 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 41 | - | v1 |
Delete a document from MCP storage
JSON-based document management tool using factory pattern
Get agent information from MCP client. Captures agent name, version, and prompt prefix from the MCP session. Caches the result in ServerExtensions for subsequent calls. Returns formatted agent information with explicit display instruction.
Get combined content from a category
Get the current project name
Get content of a file
Get project configuration settings and values. This is a read-only operation that displays current configuration without making changes. If project cannot be determined, returns null project with instructions to fix.
Get schema for a specific tool or model
Get all available schemas for tools and models
List all configured categories
List all configured collections
List all documents in a category
List all available prompts
REQUIRES EXPLICIT USER INSTRUCTION: Only use when user specifically requests category removal. This operation will permanently remove the category from project configuration and cannot be undone. Do not use without clear user intent to delete a category.
Remove a collection from the project configuration
Search across all categories for content matching the query. This is a read-only operation that finds and displays matching content without making changes.
Update project configuration settings. Use when user explicitly requests changing a specific configuration value. This operation modifies the project configuration and affects system behavior.
Set multiple project configuration values at once. Use when user explicitly requests updating multiple configuration settings. This operation modifies the project configuration and affects system behavior.
Switch to a different project
Update an existing category configuration. Use when user explicitly requests modifying category settings. This operation modifies the project configuration.
Update collection configuration and description. Use when user explicitly requests modifying collection settings. This operation modifies the project configuration.
Update an existing document in MCP storage
Many tool descriptions are under 50 characters and lack context for when to use them vs similar tools. E.g., 'Get content of a file' (guide_get_file_content) does not explain when to use this vs guide_search_content or guide_get_category_content. This ambiguity forces LLMs to guess and increases selection errors.
Output schemas are not documented anywhere in the provided code. LLMs cannot predict what fields to expect from tools like guide_search_content, guide_list_documents, or guide_get_agent_info. This forces agents to guess, parse unstructured output, or make unnecessary follow-up discovery calls.
Error handling provides no recovery guidance. No tool describes what errors it can return, what caused them, or how to recover. If guide_switch_project fails, the agent does not know whether to retry, ask the user, or try a different tool. This violates the recovery-guide pattern.
Destructive tools (guide_delete_mcp_document, guide_remove_category, guide_remove_collection) lack any confirmation or dry-run capability. An agent could delete multiple documents or categories without safeguards. No description warns of irreversibility or advises a confirmation step.
Significant tool duplication. guide_add_category exists alongside guide_categories (action='create'). guide_update_collection exists alongside guide_collections (action='update'). Agents face cognitive overhead deciding which to use, and no guidance clarifies when each is appropriate. This violates the single-namespace principle.
Parameter naming is inconsistent. Some tools use 'name' (guide_remove_category), others use 'category' (guide_list_mcp_documents). This forces LLMs to re-parse schemas and increases mismatch errors when chaining tools.