CleanSlice
Server Details
Architecture docs and patterns for NestJS + Nuxt full-stack apps
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- CleanSlice/mcp
- GitHub Stars
- 18
- Server Listing
- CleanSlice MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolsget-startedInspect
⚠️ CRITICAL: request this tool first before creating any code! Returns essential slice creation rules. READ THIS FIRST before creating any slices! Contains the MOST IMPORTANT naming rule: ALWAYS use SINGULAR names (user/ not users/).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list-categoriesInspect
List all available documentation categories. Use this to discover what categories are available before searching.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
read-docAInspect
Read the full content of a specific document by path. Use this after search to get the complete document when snippets are not enough.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Document path from search results |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. 'Full content' disclaims partial/summary results, but lacks disclosure about return format, encoding, size limits, or idempotency that would help an agent handle the response correctly.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. First sentence declares purpose; second gives precise workflow guidance. Front-loaded and appropriately sized for the complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Complete for a single-parameter read operation. Lacks output format specification (text vs. binary), but given the simplicity, 100% schema coverage, and clear usage pattern, it provides sufficient context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with 'Document path from search results'. Description adds workflow context by specifying the path comes from `search` results and reinforcing the temporal relationship (use after search), adding semantic value beyond the schema's static description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb (Read) + resource (document) + scope (full content by path). Effectively implies distinction from `search` sibling which returns snippets, though could explicitly contrast with 'get-started' or 'list-categories'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Excellent explicit guidance: 'Use this after `search`' names the prerequisite tool, and 'when snippets are not enough' defines the specific trigger condition for invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchInspect
Search for relevant documentation. Use list-categories first to see available categories. Filter by query text, framework, phase, feature, category, or tags. Returns documents sorted by relevance.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Array of tags to filter by | |
| limit | No | Max results to return (default: 5) | |
| phase | No | Development phase to filter by | |
| query | No | Search query text (searches in document names, descriptions, and keywords) | |
| offset | No | Number of results to skip for pagination (default: 0) | |
| feature | No | Feature name (e.g., authentication, user-management, file-upload) | |
| category | No | Category filter (e.g., quickstart, pattern, best-practices) | |
| framework | No | Framework identifier (e.g., nestjs, nuxt) | |
| sliceName | No | Name of the slice to find documentation for | |
| workingOn | No | Which application you are currently working on |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.