Skip to main content
Glama
Sign In
Debugg AI MCP

Debugg AI MCP

Official
by debugg-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Test Suite

test_suite
Destructive

Manage test suites: create, list, review per-test results, and delete by UUID or name plus project, enabling organized testing and outcome tracking.

Instructions

Manage test suites. Identify a suite by suiteUuid, or suiteName + a project identifier (projectUuid|projectName). Pass an "action":

  • "list" {projectUuid|projectName, search?, page?, pageSize?} → paginated suites with status/pass-rate.

  • "create" {name, description, projectUuid|projectName} → create a suite.

  • "results" {suiteUuid|(suiteName+project)} → suite + per-test outcomes.

  • "delete" {suiteUuid|(suiteName+project), confirm?} → soft-delete (DESTRUCTIVE; requires confirmation).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "test_suite"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo[create] Suite name.
pageNo[list] Page (1-indexed).
actionYesOperation to perform.
searchNo[list] Text filter over name/description.
confirmNo[delete] Set true to confirm deletion (when the client cannot prompt).
pageSizeNo[list] Page size (1..100).
suiteNameNoTest suite name (requires a project identifier).
suiteUuidNoTest suite UUID.
descriptionNo[create] Suite description.
projectNameNoProject name (or projectUuid).
projectUuidNoProject UUID (or projectName).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv6.1.2
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "create",
-  "run",
-  "results",
-  "delete"
-]New value: +[
+  "list",
+  "create",
+  "results",
+  "delete"
+]
    • removedInput schema / properties / targetUrl
      Removed value: -{
-  "description": "[run] Override the default test target (full URL).",
-  "type": "string"
-}
  2. Addedv3.10.0
  3. Removedv3.7.4
  4. Addedv3.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: delete is a soft-delete requiring confirmation, and the 'confirm' flag is documented as the path when the client cannot prompt. It also sketches per-action returns (paginated suites with status/pass-rate, suite plus per-test outcomes), which matters since there is no output schema. It does not say what happens to a suite's test cases on delete or whether a soft-delete can be undone.

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 one-line purpose, then a compact action->parameters->return bullet list. Every line carries routing or shape information; nothing is padding.

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 an 11-parameter, four-action tool with no output schema, the description covers identification, per-action inputs, and rough result shapes. Gaps are minor and mostly edge-case: pagination defaults, behavior when both suiteName and suiteUuid are supplied, and error handling for an unknown project.

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 already 100%, so the baseline is 3; the description earns extra by encoding the conditional rules the schema cannot express — that suiteUuid alone suffices, otherwise suiteName must be paired with projectUuid or projectName, and that 'confirm' only applies to delete.

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 ('Manage test suites') and immediately enumerates the four operations (list/create/results/delete) with their exact parameter shapes. An agent can distinguish this from test_case or project siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action-keyed bullets effectively tell the agent which call to make for listing, creating, reading results, or deleting, and specify the two valid ways to identify a suite. It stops short of explicit exclusions, e.g. it never says to use test_case for per-test details rather than test_suite.

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