Opsphere — DevOps & SRE Intelligence

Obtiene issue de Jira

jira_issue_get

Read-only

Get detailed information of a specific issue by key (e.g.: BEC-123).

Input Schema

Name	Required	Description
`fields`	No	Campos específicos a obtener (opcional, por defecto campos comunes)
`issueKey`	Yes	Key del issue (ej: BEC-123, STORE-456)
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / family

Added value: +{
+  "const": "jira",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / issues

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / maxResults
```
Removed value: -{
-  "type": "number"
-}
```
removedOutput schema / properties / data / properties / nextPageToken
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

addedOutput schema / properties / data / properties / operation

Added value: +{
+  "const": "jira_issue_get",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / records

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "assignee": {
+        "type": "string"
+      },
+      "body": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "environment": {
+        "type": "string"
+      },
+      "facts": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "value": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "boolean"
+                },
+                {
+                  "type": "null"
+                },
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "number",
+                      "boolean",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                }
+              ]
+            }
+          },
+          "required": [
+            "name",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "priority": {
+        "type": "string"
+      },
+      "project": {
+        "type": "string"
+      },
+      "reporter": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "facts"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / results

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / startAt
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / total / minimum
```
Added value: +0
```
changedOutput schema / properties / data / properties / total / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "family",
+  "operation",
+  "records",
+  "total",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare this as a safe read-only, non-destructive operation. The description adds no behavioral context beyond that, such as authentication expectations, rate limits, or caveats about what 'detailed information' includes.

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 wasted text. It states the core action and the identifying input immediately.

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?

For a simple read tool with full schema coverage, annotations, and an output schema, the description is minimally sufficient to invoke it with a key. However, it omits context that would help an agent choose between this and the overlapping jira_issue_fulldetails sibling.

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 description coverage is 100%, so the schema already documents all three parameters. The description restates the required issueKey example but adds no extra semantics for fields or context_id, making the baseline 3 appropriate.

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 gives a specific verb and resource: retrieving detailed information for a specific issue by key, with an example key format. It distinguishes itself from list/search siblings, but does not differentiate from jira_issue_fulldetails, which appears to overlap with 'detailed information.'

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?

Usage is implied: call this when you already have a Jira issue key and need its details. There is no explicit guidance on when to prefer this over jira_issue_fulldetails, jira_issue_comments, or search/list alternatives.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?