Skip to main content
Glama
qase-tms

Qase MCP Server

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

Search with QQL

qql_search
Read-onlyIdempotent

Search Qase entities across projects with QQL filtering, sorting, and aggregation, and fetch many records in one call instead of looping over individual get requests. Run qql_help first for syntax.

Instructions

Search any entity with Qase Query Language — filtering, cross-project, sorting, aggregation — and the right way to fetch many records at once instead of looping over qase_get. Call qql_help first for syntax, fields and enum values. Use qase_get when you already know the one ID you want. Cost: one API call, 0.5-0.9s per page; ten records here cost 1.2s against 5.3s as ten qase_get calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10, max: 100)
queryYesQQL query expression. Examples: - entity = "case" and project = "DEMO" and status = "Actual" - entity = "defect" and severity = "blocker" and status = "open" - entity = "result" and status = "failed" and ended >= now("-7d") - entity = "run" and milestone ~ "Sprint 12" See QQL documentation for full syntax and examples.
offsetNoNumber of results to skip for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "entities": {
-      "description": "Matching entities",
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total matching entities",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "total",
-    "entities"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / query / description
      Previous value: -"QQL query expression. Examples:\n- entity = \"case\" and project = \"DEMO\" and status = \"Actual\"\n- entity = \"defect\" and severity = \"blocker\" and status = \"open\"\n- entity = \"result\" and status = \"failed\" and created >= now(\"-7d\")\n- entity = \"run\" and milestone ~ \"Sprint 12\"\nSee QQL documentation for full syntax and examples."New value: +"QQL query expression. Examples:\n- entity = \"case\" and project = \"DEMO\" and status = \"Actual\"\n- entity = \"defect\" and severity = \"blocker\" and status = \"open\"\n- entity = \"result\" and status = \"failed\" and ended >= now(\"-7d\")\n- entity = \"run\" and milestone ~ \"Sprint 12\"\nSee QQL documentation for full syntax and examples."
    • changedInput schema / properties / query / maxLength
      Previous value: -1000New value: +2000
  3. Changed1 schema field changedv2.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "entities": {
+      "description": "Matching entities",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total matching entities",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "entities"
+  ],
+  "type": "object"
+}
  4. First observedv1.1.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds valuable context beyond them: per-page latency (0.5-0.9s), page-based costing, and a measured comparison against the loop alternative (1.2s vs 5.3s). It stops short of describing the result shape or pagination termination 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?

Front-loaded with the core purpose, then routing (qql_help), then the alternative (qase_get), then cost evidence. Four compact sentences, none redundant, all actionable.

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?

For a search tool with no output schema, the description covers purpose, prerequisites, alternative routing, and cost/pagination framing. It could say more about what a page of results looks like, but nothing essential to invoking 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 all three parameters (query, limit, offset) are already documented with examples. The description's 'per page' phrasing hints at paging but adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 ('Search any entity with Qase Query Language') and enumerates scope: filtering, cross-project, sorting, aggregation. It explicitly contrasts with the sibling qase_get, so an agent can tell the two apart without opening a 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 explicit when-to-use ('the right way to fetch many records at once instead of looping over qase_get'), a prerequisite ('Call qql_help first for syntax, fields and enum values'), and an alternative with its selecting condition ('Use qase_get when you already know the one ID you want').

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