Skip to main content
Glama
qase-tms

Qase MCP Server

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

Create or update test run

qase_run_upsert

Create or update a Qase test run to serve as the container for recording test results; supply a run ID to update an existing run or omit it to open a new one.

Instructions

Create or update a test run. Without id it opens a new run; with id it updates that one. A run is the container results are recorded into, so open it before calling qase_result_record. Optionally scope it to a milestone, an environment, a plan, or an explicit list of case IDs. To build a run from a suite or plan without listing cases yourself, use qase_regression_run. For a CI job that has already finished, use qase_ci_report instead — it opens the run, files the results and closes it in one call, so no half-finished run is left behind. Cost: one API call, about 0.5s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRun ID — if provided, this is an update (note: Qase API has limited run update support)
codeYesProject code (2-10 uppercase letters, numbers, or underscores)
tagsNoTag names, e.g. ["nightly", "smoke"]
casesNoCase IDs to include
titleYesRun title
plan_idNoTest plan to base run on
end_timeNoRFC3339 end time
start_timeNoRFC3339 start time
descriptionNoWhat this run covers
is_autotestNoTrue when the run is produced by automation rather than a person
custom_fieldNoCustom field values keyed by field ID, e.g. { "12": "value" }
milestone_idNoID of the milestone the run belongs to
environment_idNoID of the environment the run executes against

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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: +"What this run covers"
    • addedInput schema / properties / environment_id / description
      Added value: +"ID of the environment the run executes against"
    • addedInput schema / properties / is_autotest / description
      Added value: +"True when the run is produced by automation rather than a person"
    • addedInput schema / properties / milestone_id / description
      Added value: +"ID of the milestone the run belongs to"
    • addedInput schema / properties / tags / description
      Added value: +"Tag names, e.g. [\"nightly\", \"smoke\"]"
  2. Addedv2.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already signal this is a non-read, non-idempotent write, and the description builds on that by explaining create-vs-update behavior, the need to open a run before recording results, and that qase_ci_report avoids leaving half-finished runs. It adds meaningful operational context without contradicting annotations, though it could more prominently surface Qase's limited update support.

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?

Five sentences with zero waste: the core operation and id-based mode switch are front-loaded, followed by lifecycle context, alternatives, and cost. Every sentence earns its place, and none of it merely repeats the schema.

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 13-parameter mutation tool with no output schema, the description covers operation mode, sequencing with qase_result_record, alternative sibling tools, optional scoping, and cost. The schema covers detailed field semantics, so the agent has everything necessary to select and invoke the tool correctly.

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 value by mapping id to the create/update control flow and grouping optional parameters into meaningful scoping dimensions (milestone, environment, plan, explicit case IDs). This helps an agent decide which parameters matter, even though per-field details are left to the schema.

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?

The description names a clear verb-resource pair ('Create or update a test run') and immediately disambiguates the two modes by presence of id. It also distinguishes itself from siblings such as qase_regression_run, qase_ci_report, and qase_result_record, so an agent can tell it apart without opening the 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?

The description explicitly tells the agent when to call this tool ('open it before calling qase_result_record') and when not to: use qase_regression_run for suite/plan expansion and qase_ci_report for finished CI jobs. This is strong when/when-not routing guidance.

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