Skip to main content
Glama
qase-tms

Qase MCP Server

Official
by qase-tms
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Bulk create test cases

qase_case_bulk_create

Create up to 100 test cases in a single Qase API call to cut per-case overhead when adding many cases at once. Use for bulk creation only; update existing cases separately.

Instructions

Create up to 100 test cases in one request — the batch form of qase_case_upsert, and the right tool whenever more than one case is being written. Same fields and enum handling as qase_case_upsert; creates only, update through qase_case_upsert with id. Cost: one API call regardless of batch size — ten cases measured 1.2s against 5.6s as ten separate calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code, e.g. DEMO
casesYesTest cases to create, 1 to 100 per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "step": {
+    "properties": {
+      "action": {
+        "description": "Step action (classic steps). Not needed when `shared` is set.",
+        "type": "string"
+      },
+      "attachments": {
+        "description": "Hashes from qase_attachment_upload",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "data": {
+        "description": "Test data",
+        "type": "string"
+      },
+      "expected_result": {
+        "description": "Expected result",
+        "type": "string"
+      },
+      "shared": {
+        "description": "Hash from `qase_shared_step_upsert` to reuse here; then `action` is not needed.",
+        "type": "string"
+      },
+      "shared_step_hash": {
+        "description": "Alias for `shared`, the spelling a case reads back.",
+        "type": "string"
+      },
+      "steps": {
+        "description": "Nested substeps, nesting further if needed.",
+        "items": {
+          "$ref": "#/$defs/step"
+        },
+        "type": "array"
+      },
+      "value": {
+        "description": "Gherkin scenario text (when steps_type is \"gherkin\")",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+}
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / cases / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / cases / items / properties / attachments / description
      Previous value: -"Attachment hashes from qase_attachment_upload"New value: +"Hashes from qase_attachment_upload"
    • changedInput schema / properties / cases / items / properties / automation / description
      Previous value: -"Automation status (label, slug, or numeric ID: 0=Manual / is-not-automated, 1=To be automated, 2=Automated)"New value: +"Automation: 0=Manual, 1=To be automated, 2=Automated (label or ID)"
    • changedInput schema / properties / cases / items / properties / custom_field / description
      Previous value: -"Custom field values keyed by field ID, e.g. { \"12\": \"value\" }"New value: +"Custom fields by ID, e.g. { \"12\": \"value\" }"
    • addedInput schema / properties / cases / items / properties / custom_field / propertyNames
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / cases / items / properties / is_flaky / description
      Previous value: -"Is flaky label or numeric ID (0=No, 1=Yes). A boolean is accepted too."New value: +"Is flaky: 0=No, 1=Yes; a boolean works too."
    • addedInput schema / properties / cases / items / properties / steps / items / $ref
      Added value: +"#/$defs/step"
    • removedInput schema / properties / cases / items / properties / steps / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / cases / items / properties / steps / items / properties
      Removed value: -{
-  "action": {
-    "description": "Step action (classic steps). Not needed when `shared` is set.",
-    "type": "string"
-  },
-  "attachments": {
-    "description": "Attachment hashes from qase_attachment_upload",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "data": {
-    "description": "Test data",
-    "type": "string"
-  },
-  "expected_result": {
-    "description": "Expected result",
-    "type": "string"
-  },
-  "shared": {
-    "description": "Hash of an existing shared step to insert at this position, from `qase_shared_step_upsert`. The step then reuses that shared step instead of defining its own content, so `action` can be omitted. Reading the case back reports the link as `shared_step_hash`.",
-    "type": "string"
-  },
-  "shared_step_hash": {
-    "description": "Alias for `shared` — the name used when reading a case. Sent to the API as `shared`.",
-    "type": "string"
-  },
-  "steps": {
-    "description": "Nested substeps. Same structure as parent steps, supports further nesting.",
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "action": {
-          "description": "Step action (classic steps). Not needed when `shared` is set.",
-          "type": "string"
-        },
-        "attachments": {
-          "description": "Attachment hashes from qase_attachment_upload",
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "data": {
-          "description": "Test data",
-          "type": "string"
-        },
-        "expected_result": {
-          "description": "Expected result",
-          "type": "string"
-        },
-        "shared": {
-          "description": "Hash of an existing shared step to insert at this position, from `qase_shared_step_upsert`. The step then reuses that shared step instead of defining its own content, so `action` can be omitted. Reading the case back reports the link as `shared_step_hash`.",
-          "type": "string"
-        },
-        "shared_step_hash": {
-          "description": "Alias for `shared` — the name used when reading a case. Sent to the API as `shared`.",
-          "type": "string"
-        },
-        "value": {
-          "description": "Gherkin scenario text (when steps_type is \"gherkin\")",
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "value": {
-    "description": "Gherkin scenario text (when steps_type is \"gherkin\")",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / cases / items / properties / steps / items / type
      Removed value: -"object"
    • changedInput schema / properties / cases / items / properties / steps_type / description
      Previous value: -"How steps are written: \"classic\" action/expected pairs, or \"gherkin\" scenario text"New value: +"Step style: \"classic\" action/expected, or \"gherkin\" scenario text"
    • changedInput schema / properties / code / description
      Previous value: -"Project code (2-10 uppercase letters, numbers, or underscores)"New value: +"Project code, e.g. DEMO"
  2. Addedv2.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false. The description adds that this tool creates only (never updates), the 100-case batch ceiling, and a concrete cost profile (one API call, 1.2s vs 5.6s). It stops short of disclosing failure behavior for a partially invalid batch, which is the notable residual gap.

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?

Front-loads the limit and the sibling relationship before the cost justification. The benchmark sentence is longer than strictly necessary but does earn its place by justifying batch use over loops.

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?

A 2-parameter batch-create tool with full schema coverage and no output schema needs little more. The one gap is atomicity: the description doesn't say whether a bad case rejects the whole batch or is skipped, which matters for a 100-item call.

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 batch fields and step structure are already documented in the schema. The description adds only that field and enum handling match qase_case_upsert, which is a light pointer rather than new per-parameter meaning.

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?

States a specific verb (create) and resource (test cases) with scope (up to 100 per request) and explicitly positions itself as the batch form of qase_case_upsert. An agent can distinguish it from the single-case sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule — 'the right tool whenever more than one case is being written' — and names the alternative for the other case (update through qase_case_upsert with `id`). Both when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools