Zentao 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 |
|---|---|
| rdms_get_bugA | Get bug details by ID with image extraction. Returns bug information including image URLs but NOT image content. If you need to analyze image content, use the rdms_download_image tool with the returned image URLs. |
| rdms_get_market_bugA | Get market bug details by ID with image extraction. Returns market bug information including image URLs but NOT image content. If you need to analyze image content, use the rdms_download_image tool with the returned image URLs. |
| rdms_get_my_bugsC | Get bugs assigned to current user |
| rdms_get_my_market_bugsB | Get market bugs assigned to current user |
| rdms_download_imageC | Download and optionally analyze image from RDMS system |
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 5 tools
The tools are mostly distinct with clear purposes: two for getting bug details (regular and market), two for listing assigned bugs (regular and market), and one for downloading images. However, rdms_get_bug and rdms_get_market_bug could potentially be confused as they both retrieve bug details, differentiated only by 'market' vs. regular, but their descriptions clarify this distinction.
All tool names follow a consistent snake_case pattern with the prefix 'rdms_' and a clear verb_noun structure (e.g., 'download_image', 'get_bug', 'get_my_bugs'). This consistency makes the tool set predictable and easy to understand.
With 5 tools, the count is reasonable for a bug tracking domain, covering key operations like retrieving bug details and lists. It's slightly lean but functional, as it includes core read operations and an image download utility, though it might benefit from additional tools for broader CRUD coverage.
The tool set focuses on read operations and image handling, with no tools for creating, updating, or deleting bugs, which are typical in bug tracking systems. This creates notable gaps in lifecycle coverage, though agents can still perform basic retrieval and analysis tasks with the provided tools.