Skip to main content
Glama

Jira

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Jira Get Project

jira_get_project
Read-onlyIdempotent

Get details for a specific Jira project by key (e.g., 'PROJ') or ID. Returns name, description, lead, issue types, and custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYesProject key (e.g., "PROJ") or numeric project ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoProject ID
keyNoProject key
urlNoProject URL
leadNoProject lead user details
nameNoProject name
selfNoAPI URL for this project
errorNoError code if connection failed
styleNoProject style
expandNoExpansion options applied
messageNoError message if connection failed
favouriteNoWhether user has marked as favorite
isPrivateNoWhether project is private
avatarUrlsNoProject avatar URLs
componentsNoProject components
issueTypesNoAvailable issue types in project
simplifiedNoWhether project uses simplified workflow
descriptionNoProject description
projectTypeKeyNoProject type (software, service_desk, business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "avatarUrls": {
+      "description": "Project avatar URLs",
+      "type": "object"
+    },
+    "components": {
+      "description": "Project components",
+      "type": "array"
+    },
+    "description": {
+      "description": "Project description",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "expand": {
+      "description": "Expansion options applied",
+      "type": "string"
+    },
+    "favourite": {
+      "description": "Whether user has marked as favorite",
+      "type": "boolean"
+    },
+    "id": {
+      "description": "Project ID",
+      "type": "string"
+    },
+    "isPrivate": {
+      "description": "Whether project is private",
+      "type": "boolean"
+    },
+    "issueTypes": {
+      "description": "Available issue types in project",
+      "type": "array"
+    },
+    "key": {
+      "description": "Project key",
+      "type": "string"
+    },
+    "lead": {
+      "description": "Project lead user details",
+      "type": "object"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "name": {
+      "description": "Project name",
+      "type": "string"
+    },
+    "projectTypeKey": {
+      "description": "Project type (software, service_desk, business)",
+      "type": "string"
+    },
+    "self": {
+      "description": "API URL for this project",
+      "type": "string"
+    },
+    "simplified": {
+      "description": "Whether project uses simplified workflow",
+      "type": "boolean"
+    },
+    "style": {
+      "description": "Project style",
+      "type": "string"
+    },
+    "url": {
+      "description": "Project URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "project_key": "PROJ"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructiveness. Beyond these, the description adds that it returns specific fields (name, description, lead, etc.), providing useful behavioral context. No contradictions.

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 sentence that directly states the tool's purpose and output, with no extraneous content.

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

Completeness5/5

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

Given the simple input (one required parameter) and the presence of an output schema, the description sufficiently covers what the tool does and what it returns. No additional context needed.

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%, with the schema describing project_key as 'Project key (e.g., "PROJ") or numeric project ID'. The description repeats this example ('e.g., PROJ'), adding minimal extra meaning. Baseline 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 clearly states the tool retrieves details for a specific Jira project by key or ID, listing return fields (name, description, lead, issue types, custom fields). This distinguishes it from siblings like jira_list_projects and jira_get_issue.

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?

The description specifies the input method (key or ID) and implicitly indicates use when a known project's details are needed. However, it does not explicitly mention when not to use or alternatives, though the context is clear.

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

All Jira toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources