IA-QA — 152 QA & Dev Tools for AI Agents

search_jira_issues

Read-only

Search Jira using JQL (Jira Query Language). Returns matching issues with key fields. Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component. BYOK — credentials transit in-memory only, never stored.

Input Schema

Name	Required	Description
`jql`	Yes	JQL query string, e.g. "project = PROJ AND status = Open AND assignee = currentUser() ORDER BY priority DESC"
`fields`	No	Fields per issue. Default: summary, status, assignee, priority, issuetype, labels, created, updated
`jira_email`	Yes	Atlassian account email
`jira_token`	Yes	Atlassian API token
`max_results`	No	Max issues to return (default: 10, max: 50)
`jira_base_url`	Yes	Atlassian base URL, e.g. "https://mycompany.atlassian.net"

Output Schema

Name	Required	Description	Default
`jql`	No
`total`	No
`issues`	No
`returned`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / examples

Added value: +[
+  {
+    "jira_base_url": "https://yourcompany.atlassian.net",
+    "jira_email": "you@example.com",
+    "jira_token": "<your-atlassian-token>",
+    "jql": "project = PROJ AND status = \"To Do\""
+  }
+]

Changed1 schema field changedJun 21, 2026

addedOutput schema / properties

Added value: +{
+  "issues": {
+    "items": {
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "jql": {
+    "type": "string"
+  },
+  "returned": {
+    "type": "number"
+  },
+  "total": {
+    "type": "number"
+  }
+}

Changed1 schema field changedJun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedJun 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world semantics, so the description's real contribution is the BYOK disclosure — credentials transit in-memory only and are never stored — which an agent cannot infer from any structured field. It stops short of mentioning pagination/result caps or JQL error behavior, so 4 not 5.

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?

Three short sentences: what it does, what it returns, when to use it, then the credential caveat. Nothing is repeated and the core operation is front-loaded.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers the one thing structured data omits — that four credentials are required and handled in-memory — leaving only minor gaps like result limits and rate limits.

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 every parameter (jql, fields, max_results, and the three auth fields) is documented inline, so the baseline of 3 applies. The description adds no parameter-level meaning beyond naming JQL and 'key fields'.

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?

Names the specific verb+resource ('Search Jira using JQL') and states the return ('matching issues with key fields'). It doesn't differentiate itself from the sibling fetch_jira_issue (single-issue retrieval vs. query-based search), which keeps it at 4 rather than 5.

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 'Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component' clause implies when to reach for this tool, but there is no explicit when-not guidance and no named alternative (fetch_jira_issue, fetch_confluence_page) to route the agent away.

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

All IA-QA — 152 QA & Dev Tools for AI Agents 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.