Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

deleteTest

Permanently deletes a test and its associated data using the provided session ID.

Instructions

Delete a test by session ID. This permanently removes the test and its associated data.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "deleteTest"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe session ID of the test to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load, and it does disclose the key trait that this is irreversible and cascades to 'associated data'. It omits other behavior an agent would want: required permissions, whether in-flight tests can be deleted, and whether deletion 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?

Two short sentences with the action first and the destructive consequence immediately after. Nothing extraneous, and the most important fact (permanence) is front-loaded.

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 a single-parameter deletion tool with a fully described schema and no output schema, the description covers the essential facts: what is removed, what identifies it, and that removal is permanent. The only real omission is any precondition about test state before deletion.

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 coverage is 100%, so sessionId is already documented as 'The session ID of the test to delete'. The description's 'by session ID' repeats that rather than adding format or sourcing detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Delete a test') plus the identifying key ('by session ID'), which cleanly separates it from siblings like deleteBuild or deleteStorageFile. It falls short of 5 only because it doesn't explicitly name a contrasting alternative such as stopTest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to choose this over stopTest (halt without removal) or updateTest, and no prerequisites stated, such as whether a running test must be stopped first. The agent must infer all of this from sibling names alone.

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