iRAG 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 |
|---|---|
| generate_imageC | 使用百度iRAG API生成图片 |
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 possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as generating images using the iRAG API.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'generate_image' follows a clear verb_noun pattern.
One tool is too few for a server named 'iRAG MCP Server', which suggests a broader scope related to retrieval-augmented generation. This feels thin and limits functionality to just image generation.
The server is severely incomplete; it only offers image generation, missing core iRAG operations like querying, retrieving information, or text generation. This gap will likely cause agent failures in typical iRAG workflows.