Skip to main content
Glama
snowild

Redmine MCP Server

by snowild

get_trackers

Retrieve all available trackers from Redmine to categorize and manage project issues effectively.

Instructions

取得所有可用的追蹤器列表

Returns:
    格式化的追蹤器列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main MCP tool handler for 'get_trackers'. Decorated with @mcp.tool() for automatic registration. Fetches trackers from RedmineClient and formats output as a table.
    @mcp.tool()
    def get_trackers() -> str:
        """
        取得所有可用的追蹤器列表
        
        Returns:
            格式化的追蹤器列表
        """
        try:
            client = get_client()
            trackers = client.get_trackers()
            
            if not trackers:
                return "沒有找到追蹤器"
            
            result = "可用的追蹤器:\n\n"
            result += f"{'ID':<5} {'名稱':<20} {'預設狀態':<12}\n"
            result += f"{'-'*5} {'-'*20} {'-'*12}\n"
            
            for tracker in trackers:
                default_status = tracker.get('default_status', {}).get('name', 'N/A')
                result += f"{tracker['id']:<5} {tracker['name']:<20} {default_status:<12}\n"
            
            return result
            
        except RedmineAPIError as e:
            return f"取得追蹤器列表失敗: {str(e)}"
        except Exception as e:
            return f"系統錯誤: {str(e)}"
  • RedmineClient helper method that performs the API call to retrieve the list of trackers from Redmine's /trackers.json endpoint.
    def get_trackers(self) -> List[Dict[str, Any]]:
        """取得追蹤器列表"""
        response = self._make_request('GET', '/trackers.json')
        return response.get('trackers', [])
  • The FastMCP server instance creation where all @mcp.tool() decorated functions are automatically registered as MCP tools.
    mcp = FastMCP("Redmine MCP")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a list and mentions a return format ('格式化的追蹤器列表'), but lacks details on permissions, rate limits, pagination, or error handling. For a read operation with zero annotation coverage, this is insufficient to inform safe and effective use.

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

Conciseness3/5

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

The description is concise with two sentences, but the second sentence ('Returns: 格式化的追蹤器列表') is redundant since it restates the purpose without adding value. It could be more front-loaded by integrating the return information into the main statement, making it slightly less efficient.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose but misses behavioral traits like data format specifics, potential side effects, or error conditions. For a tool in a server with multiple similar 'get' operations, more context is needed to ensure proper integration.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as it avoids unnecessary information.

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 tool's purpose: '取得所有可用的追蹤器列表' (Get all available trackers list). It specifies the verb '取得' (get) and resource '追蹤器列表' (trackers list), making it understandable. However, it doesn't differentiate from sibling tools like 'get_projects' or 'get_priorities' beyond the resource name, which slightly limits clarity.

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. It doesn't mention prerequisites, context, or exclusions, and with siblings like 'get_projects' and 'get_priorities', there's no indication of how 'trackers' relate to or differ from these other resources. This leaves usage ambiguous.

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/snowild/redmine-mcp'

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