Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Test Suite

test_suite
Destructive

List, create, run, and delete test suites. Retrieve test results and manage suites by UUID or name with project.

Instructions

Manage and run 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.

  • "run" {suiteUuid|(suiteName+project), targetUrl?} → run all tests async. Poll with action:"results".

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

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

Input Schema

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

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Beyond annotations (destructiveHint=true), the description adds context like soft-delete and async polling. It clearly states 'DESTRUCTIVE; requires confirmation' and explains the polling mechanism.

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?

The description is structured with clear bullet-like formatting for each action, making it easy to scan. It is comprehensive without unnecessary verbosity.

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?

Despite no output schema, the description covers all five actions, required parameters, constraints (suite+project identifier), and async behavior. It is sufficiently complete for a management tool.

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?

Input schema has 100% description coverage, but the description groups parameters by action (e.g., '[list] search?, page?, pageSize?'), adding a higher-level mapping that eases understanding.

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 clearly states 'Manage and run test suites' and lists specific actions (list, create, run, results, delete), providing a specific verb and resource. It distinguishes from sibling tools like test_case and project by focusing on suites.

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 description gives explicit guidance per action, including polling after 'run', and confirmation for 'delete'. However, it does not explicitly compare with sibling tools or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/debugg-ai/debugg-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server