Skip to main content
Glama
yuezheng2006

Personal JIRA MCP

by yuezheng2006

get_project

Retrieve JIRA project details by providing the project key to access essential information for project management and tracking.

Instructions

获取JIRA项目详情

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYes

Implementation Reference

  • The handler implementation for the 'get_project' tool. This function is decorated with @mcp.tool, takes a project_key parameter, retrieves the JIRA client, fetches the project details, and returns them as a dictionary or an error message.
    @mcp.tool(
        description="获取JIRA项目详情",
    )
    def get_project(
        project_key: str
    ) -> Dict[str, Any]:
        """获取项目详情.
        
        Args:
            project_key: 项目键
        
        Returns:
            Dict[str, Any]: 项目详情
        """
        logger.info(f"获取项目: {project_key}")
        try:
            client = get_jira_client()
            project = client.project(project_key)
            
            return {
                "id": project.id,
                "key": project.key,
                "name": project.name,
                "lead": getattr(project, "lead", {}).get("displayName", ""),
                "description": getattr(project, "description", ""),
                "url": project.self,
            }
        except Exception as e:
            logger.error(f"获取项目 {project_key} 失败: {str(e)}")
            return {"error": str(e)}
  • Helper function that creates and caches a JIRA client instance using settings from config. Called within the get_project handler.
    def get_jira_client() -> JIRA:
        """获取JIRA客户端实例."""
        global jira_client
        if jira_client is None:
            auth = get_jira_auth()
            jira_client = JIRA(server=jira_settings.server_url, basic_auth=auth)
        return jira_client
  • The mcp.run() call in main() that starts the MCP server and registers all @mcp.tool decorated functions, including get_project.
    mcp.run(transport=args.transport)
  • Initialization of the FastMCP server instance which handles tool registration via decorators.
    mcp = FastMCP("JIRA MCP Server", port=int(os.getenv("MCP_SERVER_PORT", "8000")))
Behavior1/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 only states the action ('获取' - get) without describing what '获取' entails—e.g., whether it's a read-only operation, requires authentication, has rate limits, returns structured data, or handles errors. This leaves the agent with insufficient information about how the tool behaves.

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 extremely concise—a single phrase in Chinese—and front-loaded with the core action. There's no wasted text, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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

Completeness1/5

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

Given the tool's complexity (a read operation with 1 parameter), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter details, or return values, leaving the agent unprepared to use the tool effectively.

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

Parameters1/5

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

The description adds no meaning beyond the input schema. With 0% schema description coverage and 1 parameter ('project_key'), the schema only provides a title and type. The description doesn't explain what 'project_key' is (e.g., a JIRA identifier like 'PROJ-123'), its format, or examples. This fails to compensate for the low schema coverage.

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

Purpose3/5

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

The description '获取JIRA项目详情' (Get JIRA project details) states a clear verb ('获取' - get) and resource ('JIRA项目' - JIRA project), but it's vague about what '详情' (details) includes. It doesn't distinguish from sibling 'get_projects' (which likely lists multiple projects) or 'get_issue' (which gets issue details). The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention when to use it over 'get_projects' (for listing projects) or 'get_issue' (for issue details), nor does it specify prerequisites like needing a project key. The description alone offers no usage context.

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