Skip to main content
Glama

jira_get_project

Retrieve detailed information for a Jira project by key, including description, lead, issue types, and components. Find available project keys with jira_get_projects first.

Instructions

Get detailed information about a specific Jira project including description, lead, issue types, and components. Use jira_get_projects first to find available project keys.

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": {
      "projectKey": "<projectKey>"
    },
    "name": "jira_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key (e.g., KP, PROJ). Get from jira_get_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only lookup and usefully lists the returned content, but says nothing about error behavior for an invalid or inaccessible key, permissions, or whether components and issue types are truncated or complete.

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?

Two sentences, both earning their place: the first defines scope and payload, the second is front-loaded prerequisite guidance. No padding or repetition.

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

Completeness4/5

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

For a one-parameter read tool with no output schema and no annotations, the description adequately covers what is returned and how to obtain the required key. Only failure modes and pagination of nested collections are left unaddressed.

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?

Schema coverage is 100% and the single projectKey parameter already documents format ("KP, PROJ") and sourcing. The description's mention of finding keys via jira_get_projects echoes the schema rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb and resource ("Get detailed information about a specific Jira project") and enumerates the fields included (description, lead, issue types, components), which lets an agent distinguish it from the plural listing sibling jira_get_projects. Differentiation relies on the word "specific" rather than an explicit contrast statement, so it falls just short of the top score.

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

Usage Guidelines4/5

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

"Use jira_get_projects first to find available project keys" supplies a concrete prerequisite that shapes the call sequence. It gives no exclusions, though, so an agent gets no guidance on when project versions, assignable users, or other project sub-resources are the better call.

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