Ragie Model Context Protocol Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAGIE_API_KEY | Yes | Your Ragie API authentication key | |
| RAGIE_PARTITION | No | The Ragie partition ID to query |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieveA | Look up information in the Knowledge Base. Use this tool when you need 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 1 tool
With only one tool, there is no potential for confusion between tools. The tool's purpose is clearly defined.
With a single tool named 'retrieve', there is no pattern to evaluate. Naming is neither consistent nor inconsistent—it's neutral.
A knowledge base server with only one retrieval tool is extremely minimal. Agents cannot perform any CRUD operations, making this count far too low for the implied scope.
The server only supports retrieval. Essential actions like adding, updating, or deleting documents are missing, leaving significant gaps in functionality.