Skip to main content
Glama
Sign In
jira-dev-mcp

jira-dev-mcp

by nianyi778
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

jira_get_project_path

Find the local repository path for a Jira project key. Input the project key to retrieve its mapped directory on your filesystem.

Instructions

Get the local repository path mapped to a Jira project key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jiraProject": "<jiraProject>"
    },
    "name": "jira_get_project_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
jiraProjectYesJira project key (e.g. AT)
response_formatNoOutput format (default json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.4/5.0
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 action but does not explain what happens if no mapping exists, error behavior, or the output format. For a getter tool, this lack of context is a notable gap.

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, front-loaded sentence with no filler or redundancy. It efficiently states the action and the resource.

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?

With no output schema and no annotations, the description should explain the return format or failure behavior but only states what the tool gets. The agent is left guessing about the response structure and error handling, which is critical for a lookup tool.

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 already covers both parameters with clear descriptions (e.g., 'Jira project key (e.g. AT)'), yielding 100% schema description coverage. The description adds no extra parameter detail, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb ('Get') and resource ('local repository path mapped to a Jira project key'), clearly distinguishing it from sibling tools like jira_set_project_path or jira_search_issues. It immediately conveys the exact function.

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 when to use it (when you need the local repository path for a Jira project key) but does not explicitly state when not to use it or mention alternatives. No exclusion or comparison with sibling tools is provided, so guidance is minimal.

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

Deploy Server

Other Tools