IA-QA — 130+ QA & Dev Tools for AI Agents

jira_to_test_suite

Read-only

Transform a Jira ticket into a complete test suite: Gherkin scenarios, E2E steps, API test cases, test data matrix, and ambiguity detection. Accepts either Jira credentials (auto-fetch) or a pre-fetched issue object. The returned test_suite includes _gherkin_warnings (deterministic syntax validation — empty if clean). Requires BYOK LLM key (OpenAI, Anthropic, etc.).

Input Schema

TableJSON Schema

Name	Required	Description
`issue`	No	Pre-fetched issue object from fetch_jira_issue, OR a mock object with fields: key, summary, description (plain text or Markdown), status, issue_type, priority, labels, comments. Use this for offline/CI testing without Jira credentials.
`model`	Yes	LLM model to use, e.g. "gpt-4o-mini", "claude-3-5-haiku-20241022", "gemini-2.0-flash".
`api_key`	Yes	Your LLM provider API key (OpenAI sk-, Anthropic sk-ant-, Google AIzaSy-, etc.).
`issue_key`	No	Jira issue key to fetch automatically, e.g. "PROJ-123". Required if issue is not provided.
`jira_email`	No	Atlassian account email. Required for auto-fetch mode.
`jira_token`	No	Atlassian API token. Required for auto-fetch mode.
`max_tokens`	No	Maximum tokens for the LLM response. Default: 8192. Increase for large tickets with many ACs; decrease to reduce cost on simple tickets.
`jira_base_url`	No	Atlassian base URL. Required for auto-fetch mode.
`confluence_pages`	No	Optional array of pre-fetched Confluence page objects from fetch_confluence_page, used as documentation context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`summary`	No
`issue_key`	No
`issue_url`	No
`latency_ms`	No
`model_used`	No
`test_suite`	No
`tokens_used`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 21, 2026

addedOutput schema / properties

Added value: +{
+  "issue_key": {
+    "type": "string"
+  },
+  "issue_url": {
+    "type": "string"
+  },
+  "latency_ms": {
+    "type": "number"
+  },
+  "model_used": {
+    "type": "string"
+  },
+  "summary": {
+    "type": "string"
+  },
+  "test_suite": {
+    "type": "object"
+  },
+  "tokens_used": {
+    "type": "number"
+  }
+}

Changed2 schema fields changedJun 18, 2026
- addedInput schema / properties / confluence_pages / items / additionalProperties
```
Added value: +true
```
- addedInput schema / properties / issue / additionalProperties
```
Added value: +true
```

Changed1 schema field changedJun 10, 2026

changedOutput schema / (root)

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

Changed1 schema field changedJun 7, 2026

addedInput schema / properties / max_tokens

Added value: +{
+  "default": 8192,
+  "description": "Maximum tokens for the LLM response. Default: 8192. Increase for large tickets with many ACs; decrease to reduce cost on simple tickets.",
+  "type": "integer"
+}

Changed1 schema field changedJun 6, 2026

changedInput schema / properties / issue / description

Previous value: -"Pre-fetched issue object from fetch_jira_issue (alternative to credentials + issue_key)."New value: +"Pre-fetched issue object from fetch_jira_issue, OR a mock object with fields: key, summary, description (plain text or Markdown), status, issue_type, priority, labels, comments. Use this for offline/CI testing without Jira credentials."

AddedJun 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds valuable context: requires a BYOK LLM key, returns _gherkin_warnings with deterministic validation, and supports auto-fetch via credentials. 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?

Three sentences, front-loaded with the core transformation outcome, then modes, then key requirement and output caveat. Every sentence carries distinct information with no redundancy.

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 tool's complexity (9 params, two mutually exclusive input modes, nested objects), the description covers purpose, input modes, required external key, and an important output field (_gherkin_warnings). Output schema exists, so full return values aren't needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds the key relationship that credentials and pre-fetched issue are alternative modes, helping the agent decide whether to use issue or issue_key+jira_* parameters. This grouping insight goes beyond the schema's individual parameter descriptions.

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 opens with a specific verb+resource: 'Transform a Jira ticket into a complete test suite' and lists concrete outputs (Gherkin scenarios, E2E steps, API test cases, test data matrix, ambiguity detection). This clearly distinguishes it from sibling tools like generate_test_cases or prompt_test_suite by anchoring to Jira ticket input.

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?

It explicitly explains the two input modes: Jira credentials (auto-fetch) or a pre-fetched issue object, and the schema adds the offline/CI testing use case for the issue parameter. It does not compare against alternatives or state exclusions, so not a 5, but 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 IA-QA — 130+ 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.

Resources

Need Help?