Skip to main content
Glama

jira_get_projects

Retrieve a list of all Jira projects to view available workspaces and their details for project management and organization.

Instructions

Get list of Jira projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of jira_get_projects: fetches projects from Jira client, formats them into a list with key, name, id, and returns as JSON text content.
    async def _get_projects(self) -> List[TextContent]:
        """Get list of projects"""
        projects = self.jira_client.projects()
        
        project_list = []
        for project in projects:
            project_list.append({
                "key": project["key"],
                "name": project["name"],
                "id": project["id"]
            })
        
        return [TextContent(
            type="text",
            text=json.dumps(project_list, indent=2)
        )]
  • Tool registration in list_tools() method, defining the tool name, description, and empty input schema.
        Tool(
            name="jira_get_projects",
            description="Get list of Jira projects",
            inputSchema={
                "type": "object",
                "properties": {}
            }
        )
    ]
  • Input schema for jira_get_projects tool, which requires no parameters.
    inputSchema={
        "type": "object",
        "properties": {}
    }
  • Dispatch in the main call_tool handler that routes to the _get_projects implementation.
    elif name == "jira_get_projects":
        return await self._get_projects()
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose permissions needed, rate limits, pagination, sorting, or what data is returned. For a read tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero waste. It is front-loaded with the core purpose, making it easy to scan and understand quickly without any redundant or verbose language.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't explain return format, error conditions, or behavioral constraints, which would help an agent use it correctly despite the low complexity.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for this scenario is 4, as it avoids unnecessary repetition of schema 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 verb ('Get') and resource ('list of Jira projects'), making the purpose immediately understandable. It distinguishes this read operation from sibling tools that perform mutations like create, update, or transition. However, it doesn't specify scope (e.g., all projects vs. filtered), keeping it from a perfect score.

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

Usage Guidelines3/5

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

The description implies usage for retrieving project lists, but provides no explicit guidance on when to use this versus alternatives like jira_search_issues or jira_get_issue. No prerequisites, exclusions, or comparative context are mentioned, leaving usage decisions to inference.

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/katsuhirohonda/jira-confluence-mcp'

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