Opsphere — DevOps & SRE Intelligence

Issues recientes de un proyecto

jira_issues_recent

Read-only

Get the most recent issues in a project (sorted by update date).

Input Schema

Name	Required	Description
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`maxResults`	No
`projectKey`	No	Key del proyecto (opcional; por defecto catálogo jira_project_key, JIRA_PROJECT_KEY o JIRA_PROJECT_PREFIX)

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_issues_recent",
+  "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.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the sort order, which is useful behavioral context, but says nothing about result volume, pagination, or what happens when projectKey is omitted and no default catalog exists — omissions that matter for a listing tool capped at 100 results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler and the ordering rule placed immediately after the resource. It is efficient, though slightly under-sized for a tool whose disambiguation need is high.

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?

An output schema exists, so return shape need not be explained, and annotations cover the read-only profile. What is missing is the sibling routing and the default-limit/pagination context, which leaves the agent guessing on the two decisions this tool actually forces.

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 67%: projectKey and context_id have descriptions with fallback behavior, maxResults carries only default/min/max with no prose. The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate for moderate coverage.

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 names a specific verb and resource plus a concrete ordering rule ('sorted by update date'), which is more than a restatement of the name. However, it never contrasts itself with the near-identical siblings jira_issues_list and jira_issues_search, so an agent cannot tell from the text which one to pick.

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?

'Most recent issues in a project' implies a recency-triage use case, which is implicit guidance. There is no explicit when-to-use/when-not, no mention of the alternatives (jira_issues_search for JQL, jira_issues_list for full listing), and no prerequisite or project-scope caveat.

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?