Skip to main content
Glama
Sign In
Qase MCP Server

Qase MCP Server

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

Discover more tools

qase_discover_tools
Read-onlyIdempotent

Search Qase MCP tools by task or keyword to find matching tools and descriptions when unsure which tool to use.

Instructions

Search the tool catalogue by what you are trying to do — "delete", "milestone", "review", "custom field" — and get back the matching tools with their descriptions. Every tool is already listed and callable; use this when you do not know which one fits, rather than re-reading the whole list. Cost: no API call, matching happens in memory, about 3ms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qase_discover_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query to find tools by name or description. Examples: "delete", "milestone", "attachment", "suite"
categoryNoFilter by tool category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / activate
      Removed value: -{
-  "default": true,
-  "description": "If true (default), found tools are activated and become available for use",
-  "type": "boolean"
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "activated": {
-      "description": "Number of newly activated tools",
-      "type": "integer"
-    },
-    "found": {
-      "description": "Number of matching tools",
-      "type": "integer"
-    },
-    "tools": {
-      "items": {
-        "properties": {
-          "description": {
-            "type": "string"
-          },
-          "destructive": {
-            "type": "boolean"
-          },
-          "name": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "found",
-    "activated",
-    "tools"
-  ],
-  "type": "object"
-}New value: +null
  2. Addedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context the annotations cannot convey: no API call, in-memory matching, ~3ms cost. It does not describe result ordering or result-count limits.

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-loaded with purpose before usage guidance and cost, and there is no filler. The inline query examples overlap with the schema's own examples, which is mild redundancy, but the single-paragraph structure is tight.

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?

With no output schema, the description carries the return-value burden and does so adequately ('matching tools with their descriptions'). Both optional parameters are documented in the schema, and the cost/behavior note is present. Only result cap/ordering is unspecified.

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%, and the query examples ('milestone', 'attachment', 'suite') appear in the schema itself as well. The description adds the illustrative query terms inline but nothing about how query and category combine, so baseline 3 applies when the schema does the heavy lifting.

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 (search) and resource (the tool catalogue) plus the intent-based matching mechanism and the return value (matching tools with their descriptions). It is immediately distinguishable from every sibling, all of which are Qase domain operations rather than meta-tool discovery.

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?

Gives clear context: 'use this when you do not know which one fits, rather than re-reading the whole list.' That names the alternative behavior to avoid. It does not explicitly contrast with the closest sibling, qase_tool_help, so it falls just short of full when/when-not routing.

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