Skip to main content
Glama
qase-tms

Qase MCP Server

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

Call Qase API

qase_api

Call any Qase REST endpoint directly for operations not covered by dedicated tools. Specify HTTP method, path, body, and query parameters to interact with the Qase API.

Instructions

Call any Qase REST endpoint directly, for the few things no dedicated tool covers. Pass the HTTP method, a path starting with a version segment such as /v1/, and an optional body or query. The path must be an endpoint path on the configured Qase host; a full URL, or one that resolves to another host, is refused. See developers.qase.io for the reference. Prefer a dedicated tool wherever one exists: they normalize enums, validate arguments before spending a round trip, and shape the response for a model. This one hands back whatever the API returns. It sends JSON only and cannot upload files — multipart uploads go through qase_attachment_upload. A DELETE through this tool asks for confirmation the same way the dedicated delete tools do. Cost: one API call, typically 0.3-1.5s depending on the endpoint. No caching, no pagination help, no retries beyond the client defaults.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body for POST/PUT/PATCH
pathYesAPI path starting with a version segment (e.g., "/v1/project/DEMO/run")
queryNoQuery parameters
methodNoHTTP methodGET

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.7.4
    • changedInput schema / properties / path / description
      Previous value: -"API path starting with /v1/ (e.g., \"/v1/project/DEMO/run\")"New value: +"API path starting with a version segment (e.g., \"/v1/project/DEMO/run\")"
    • removedInput schema / properties / path / minLength
      Removed value: -1
    • addedInput schema / properties / path / pattern
      Added value: +"^\\/v\\d+\\/\\S*$"
  2. Addedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, the description discloses that it sends JSON only, cannot upload files, asks confirmation for DELETE, returns raw API responses, and has no caching, pagination, or retries. It also states typical cost/time. This substantially exceeds what annotations alone convey.

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?

The description is longer than typical, but every sentence earns its place: purpose, path constraints, alternatives, body/format limits, confirmation behavior, performance, and caveats. It is front-loaded with the core purpose and structured logically, with no repetition or 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?

For a generic passthrough tool with no output schema, the description covers path formulation, host restriction, HTTP methods, body/query, file upload exclusion, DELETE confirmation, cost, and limitations. This is sufficient for a model to decide when to call it and what to expect.

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?

All four parameters are already documented in the schema (100% coverage), so the baseline is 3. The description adds genuine extra meaning by explaining that the path must target the configured Qase host and that full URLs are refused, while also clarifying the default GET method and optional body/query.

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 ('Call') and a clear resource ('any Qase REST endpoint'), and explicitly frames it as the fallback for 'the few things no dedicated tool covers.' This differentiates it from the dedicated sibling tools immediately and explains the path format and optional body/query.

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?

Explicitly instructs to 'Prefer a dedicated tool wherever one exists' and explains why, then routes file uploads to qase_attachment_upload. This gives the agent crisp when-to-use vs. alternatives guidance with no ambiguity.

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