Skip to main content
Glama
qase-tms

Qase MCP Server

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

Triage failure into defect

qase_triage_defect

Create a defect from a test failure, capturing title, severity, and actual results so triage context is preserved. File one defect per distinct cause; reference run or result IDs in actual_result.

Instructions

Create a defect from a test failure with the context written into it; title, actual_result and severity are required. The API has no way to attach runs or results to a defect — reference them in actual_result. For a defect unrelated to a failure use qase_defect_upsert. Cost: one API call, about 0.5s; file one defect per distinct cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code, e.g. DEMO
tagsNoTag names, e.g. ["regression", "payments"]
titleYesDefect title
severityYesRequired by the API
attachmentsNoHashes from qase_attachment_upload
descriptionNoExtra context beyond the observed behavior
custom_fieldNoCustom fields by ID, e.g. { "12": "value" }
actual_resultYesObserved behavior. Required by the API

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / attachments / description
      Previous value: -"Attachment hashes from qase_attachment_upload"New value: +"Hashes from qase_attachment_upload"
    • changedInput schema / properties / code / description
      Previous value: -"Project code (2-10 uppercase letters, numbers, or underscores)"New value: +"Project code, e.g. DEMO"
    • changedInput schema / 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 / custom_field / propertyNames
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "defect": {
-      "description": "Full defect entity",
-      "type": "object"
-    },
-    "defect_id": {
-      "description": "Created defect ID",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "defect_id"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv2.5.1
    • addedInput schema / properties / custom_field / description
      Added value: +"Custom field values keyed by field ID, e.g. { \"12\": \"value\" }"
    • addedInput schema / properties / description / description
      Added value: +"Extra context beyond the observed behavior"
    • addedInput schema / properties / tags / description
      Added value: +"Tag names, e.g. [\"regression\", \"payments\"]"
  3. Changed1 schema field changedv2.2.1
    • addedInput schema / properties / attachments / description
      Added value: +"Attachment hashes from qase_attachment_upload"
  4. Changed7 schema fields changedv2.1.1
    • changedInput schema / properties / actual_result / description
      Previous value: -"Observed behavior"New value: +"Observed behavior. Required by the API"
    • removedInput schema / properties / failed_result_ids
      Removed value: -{
-  "description": "Result hashes to link to this defect (from the run)",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / run_id
      Removed value: -{
-  "description": "Run containing the failed results",
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}
    • addedInput schema / properties / severity / description
      Added value: +"Required by the API"
    • changedInput schema / required
      Previous value: -[
-  "code",
-  "title"
-]New value: +[
+  "code",
+  "title",
+  "severity",
+  "actual_result"
+]
    • removedOutput schema / properties / linked_results
      Removed value: -{
-  "description": "Number of linked result hashes",
-  "type": "integer"
-}
    • changedOutput schema / required
      Previous value: -[
-  "defect_id",
-  "linked_results"
-]New value: +[
+  "defect_id"
+]
  5. Addedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false, so the description carries the real burden and delivers: it discloses an API capability gap ('no way to attach runs or results to a defect') with the workaround of embedding references in actual_result, plus cost (~one API call, ~0.5s). It stops short of covering permissions or duplicate/error behavior.

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 dense sentences, front-loaded with the action and required fields, then the capability limitation, then the alternative tool and cost. No filler and every clause carries information.

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?

For an 8-parameter mutation with a nested custom_field object and no output schema, the definition covers required fields, the attachment/result limitation, the alternative tool, and the per-cause batching rule. Nothing needed to call it correctly is missing.

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 8 parameters including code, severity enum, attachments hashes, and custom_field shape. The description only restates which fields are required, adding no syntax or format detail beyond structured data.

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+resource+source ('Create a defect from a test failure') and names the sibling it is not for ('For a defect unrelated to a failure use qase_defect_upsert'), so an agent can route 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?

Explicit routing rule to qase_defect_upsert for the non-failure case, plus a cardinality rule ('file one defect per distinct cause') that tells the agent how many calls to make. Both when-to-use and when-not-to-use are present.

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