Skip to main content
Glama
yuezheng2006

Personal JIRA MCP

by yuezheng2006

get_projects

Retrieve a list of JIRA projects to view and manage work items through the Personal JIRA MCP server interface.

Instructions

获取JIRA项目列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_projects tool handler function decorated with @mcp.tool, which registers it and implements fetching JIRA projects list using the JIRA client, formatting them into a list of dictionaries with id, key, name, and lead.
    @mcp.tool(
        description="获取JIRA项目列表",
    )
    def get_projects() -> Dict[str, Any]:
        """获取所有项目列表.
        
        Returns:
            Dict[str, Any]: 项目列表
        """
        logger.info("获取项目列表")
        try:
            client = get_jira_client()
            projects = client.projects()
            
            result = [
                {
                    "id": project.id,
                    "key": project.key,
                    "name": project.name,
                    "lead": getattr(project, "lead", {}).get("displayName", ""),
                }
                for project in projects
            ]
            
            return {"projects": result}
        except Exception as e:
            logger.error(f"获取项目列表失败: {str(e)}")
            return {"error": str(e)}
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. The description only states what the tool does ('get JIRA project list') without revealing any behavioral traits such as whether it requires authentication, how it handles errors, if it's read-only or has side effects, or what format the output might be in. This leaves significant gaps for an AI agent to understand the tool's behavior.

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 phrase ('获取JIRA项目列表') that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It lacks behavioral context (e.g., read-only vs. mutative, authentication needs) and doesn't explain the return values or format, which is crucial since there's no output schema. For a tool interacting with a system like JIRA, more completeness is needed to guide proper usage.

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 tool has 0 parameters, and the schema description coverage is 100%, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool. No additional value is required beyond stating the tool's purpose.

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 '获取JIRA项目列表' clearly states the action ('获取' meaning 'get/fetch') and resource ('JIRA项目列表' meaning 'JIRA project list'), providing a specific verb+resource combination. However, it doesn't distinguish this from sibling tools like 'get_project' (singular), which might retrieve a single project, leaving some ambiguity about sibling differentiation.

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 when to use 'get_projects' (plural) instead of 'get_project' (singular) or other sibling tools like 'search_issues', nor does it specify any prerequisites or context for usage.

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/yuezheng2006/mcp-server-jira'

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