ragify_docs_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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ragify_docs_mcpA | Use this tool to fetch reference information, code blocks, and context from a programming framework, API, library, or website documentation URL. Returns raw, highly relevant text blocks matching your search query. |
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 1 tool
With only one tool, there is no ambiguity in tool selection; the tool's purpose is clearly defined and distinct.
A single tool trivially follows a consistent naming pattern, as there are no other tools to compare or conflict with.
One tool is borderline for a documentation-fetching server; while it may suffice for a narrow use case, typical servers offer multiple operations like listing sources or managing configurations.
The server lacks tools for managing documentation sources, such as adding, updating, or listing available URLs, which are significant gaps for a comprehensive documentation assistant.