Skip to main content
Glama
qase-tms

Qase MCP Server

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

Project context

qase_project_context
Read-onlyIdempotent

Fetch a Qase project's details, suite tree, milestones, environments, custom fields, and users in one call to build initial context before test work.

Instructions

Seed everything about a project in one call: details, the full suite tree, milestones, environments, custom fields and users — make it first when starting on a project. Each collection returns its first 100; check coverage and pass full: true to page. For one record by ID qase_get is cheaper; for filtered questions use qql_search. Cost: six API calls behind one, 0.5-1.3s cold, cached 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesProject code, e.g. DEMO
fullNoPage through every collection instead of the first 100 of each (default: false). Use it when `coverage` reports one truncated; see qase_tool_help for what it costs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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 / full / description
      Previous value: -"Page through every suite, milestone, environment, custom field, and user instead of fetching only the first 100 of each (default: false). Use this when a collection is reported as truncated and you need the complete set — it costs one API call per 100 entities and can return thousands of items, so prefer the targeted list tools or qql_search when you only need a subset."New value: +"Page through every collection instead of the first 100 of each (default: false). Use it when `coverage` reports one truncated; see qase_tool_help for what it costs."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "coverage": {
-      "description": "Per-collection completeness: each of suites, milestones, environments, custom_fields, and users maps to { total, loaded, truncated }. When truncated is true the list holds only the first `loaded` of `total` entities — re-call with full: true for the rest.",
-      "type": "object"
-    },
-    "custom_fields": {
-      "description": "Custom fields list",
-      "type": "object"
-    },
-    "environments": {
-      "description": "Environments list",
-      "type": "object"
-    },
-    "milestones": {
-      "description": "Milestones list",
-      "type": "object"
-    },
-    "project": {
-      "description": "Project details",
-      "type": "object"
-    },
-    "suites": {
-      "description": "Suites list with entities array",
-      "type": "object"
-    },
-    "users": {
-      "description": "Team members list",
-      "type": "object"
-    }
-  },
-  "required": [
-    "project",
-    "suites",
-    "milestones",
-    "environments",
-    "coverage"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv2.1.1
    • addedInput schema / properties / full
      Added value: +{
+  "description": "Page through every suite, milestone, environment, custom field, and user instead of fetching only the first 100 of each (default: false). Use this when a collection is reported as truncated and you need the complete set — it costs one API call per 100 entities and can return thousands of items, so prefer the targeted list tools or qql_search when you only need a subset.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / coverage
      Added value: +{
+  "description": "Per-collection completeness: each of suites, milestones, environments, custom_fields, and users maps to { total, loaded, truncated }. When truncated is true the list holds only the first `loaded` of `total` entities — re-call with full: true for the rest.",
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "project",
-  "suites",
-  "milestones",
-  "environments"
-]New value: +[
+  "project",
+  "suites",
+  "milestones",
+  "environments",
+  "coverage"
+]
  3. Addedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description adds real operational detail beyond them — each collection caps at 100, a `coverage` signal indicates truncation, and the cost profile (six API calls, 0.5-1.3s cold, 5-minute cache) lets the agent plan. No contradiction with the readOnlyHint.

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-loads the payload ('seed everything about a project in one call') before paging rules, sibling routing, and cost. Every clause carries a distinct decision-relevant fact with no filler.

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?

With no output schema, the description still tells the agent what comes back (the named collections, capped at 100 each) and surfaces the `coverage` field it must inspect, plus latency/caching expectations. 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema lacks: `full: true` should be driven by what `coverage` reports, and the cost of paging is deferred to qase_tool_help. That is genuine value beyond the field 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?

States a specific verb ('seed everything about a project in one call') and enumerates the exact resources covered: details, suite tree, milestones, environments, custom fields and users. It also names the siblings it is not (qase_get, qql_search), so an agent can place it immediately.

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 routing rules: 'make it first when starting on a project', 'for one record by ID qase_get is cheaper', 'for filtered questions use qql_search'. Both the when and the when-not are stated with named alternatives.

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