Skip to main content
Glama

rdms_get_my_market_bugs

Retrieve market bug reports assigned to your user from the Zentao bug tracking system. Specify result limits to streamline bug management and prioritize tasks efficiently.

Instructions

Get market bugs assigned to current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results

Implementation Reference

  • index.js:113-122 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'rdms_get_my_market_bugs',
      description: 'Get market bugs assigned to current user',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Max results', default: 20 }
        }
      }
    },
  • index.js:150-151 (registration)
    Tool dispatch case in CallToolRequestSchema switch statement.
    case 'rdms_get_my_market_bugs':
      return { content: [{ type: 'text', text: JSON.stringify(await this.getMyMarketBugs(args.limit)) }] };
  • Core handler function that performs HTTP request to fetch user's market bugs and delegates parsing.
    async getMyMarketBugs(limit = 20) {
      await this.ensureLoggedIn();
      try {
        const marketBugsUrl = `${this.baseUrl}/index.php?m=bugmarket&f=browse&productid=0&branch=0&browseType=assigntome`;
        const response = await this.client.get(marketBugsUrl);
        return this.parseBugList(response.data, limit, '市场Bug');
      } catch (error) {
        return { success: false, error: error.message, bugs: [] };
      }
    }
  • Helper function that parses the HTML response from RDMS into a structured list of bugs.
    parseBugList(html, limit = 20, type = 'BUG') {
      const $ = cheerio.load(html);
      const bugs = [];
      
      // 查找Bug链接 - 修正选择器
      const bugLinks = $('a[href*="m=bug&f=view&bugID="]');
      
      bugLinks.each((index, link) => {
        if (index >= limit) return false;
        
        const $link = $(link);
        const href = $link.attr('href');
        const title = $link.text().trim();
        
        // 提取Bug ID - 修正正则表达式
        const match = href.match(/bugID=(\d+)/);
        const bugId = match ? match[1] : '';
        
        // 获取当前行的其他信息
        const $row = $link.closest('tr');
        const severity = $row.find('.label-severity-custom').text().trim() || 
                        $row.find('[title*="严重程度"]').text().trim();
        const priority = $row.find('.label-pri').text().trim();
        const reporter = $row.find('td').eq(6).text().trim(); // 创建者列
        const resolver = $row.find('td').eq(8).text().trim(); // 解决者列
        const resolution = $row.find('td').eq(9).text().trim(); // 方案列
        
        // 只处理有效的Bug
        if (bugId && parseInt(bugId) > 0 && title && title.length > 0) {
          bugs.push({
            id: bugId,
            title: title,
            status: '', // 状态信息在这个页面中不直接显示
            priority: priority,
            severity: severity,
            assignedTo: '', // 当前用户就是被指派人
            reporter: reporter,
            resolver: resolver,
            resolution: resolution,
            created: '',
            url: href.startsWith('http') ? href : `${this.baseUrl}${href.replace(/^\.\//, '')}`
          });
        }
      });
      
      // 如果找到Bug,返回结果
      if (bugs.length > 0) {
        return {
          success: true,
          total: bugs.length,
          bugs: bugs,
          type: type,
          message: `找到 ${bugs.length} 个${type}`
        };
      }
      
      // 检查是否显示"暂时没有Bug"
      const emptyTip = $('.table-empty-tip').text().trim();
      if (emptyTip.includes('暂时没有Bug')) {
        return {
          success: true,
          total: 0,
          bugs: [],
          type: type,
          message: `暂无${type}`
        };
      }
      
      // 默认返回空结果
      return {
        success: true,
        total: 0,
        bugs: [],
        type: type,
        message: `暂无${type}`
      };
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get') but doesn't describe traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what happens if no bugs are found. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter, high schema coverage, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, usage context, and output format, which could help the agent use it more effectively. Given the simplicity, it meets a baseline level of completeness but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'limit' parameter clearly documented. The description doesn't add any parameter-specific information beyond what the schema provides, such as default behavior or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('market bugs assigned to current user'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'rdms_get_my_bugs' or 'rdms_get_market_bug', which might have overlapping functionality, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'rdms_get_my_bugs' or 'rdms_get_market_bug'. It implies usage for retrieving bugs assigned to the current user, but lacks explicit context, exclusions, or comparisons with siblings, leaving the agent to infer usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ad19900913/mcp-rdms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server