Skip to main content
Glama
Sign In
M00N Report MCP

M00N Report MCP

Official
by m00nreport
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Local

delete_test_case

DestructiveIdempotent

Archive a test case by ID, removing it from active use while allowing restores via the UI. Unlinks any connected autotests.

Instructions

Soft delete (archive) a test case. The case can be restored via the UI. Also unlinks any connected autotests.

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": {
      "caseId": "<caseId>"
    },
    "name": "delete_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseIdYesNumeric test case ID to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description adds valuable behavioral details: the operation is a soft delete, the case can be restored via the UI, and connected autotests are unlinked. These side effects are not visible from annotations alone and help the agent predict the full impact.

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 two tight sentences with no wasted words. The core operation is front-loaded, followed by the restore path and the important side effect of unlinking autotests.

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 simple one-parameter mutation with annotations, this description is sufficient. It explains what happens, how it can be undone, and what additional effects occur, so an agent can safely predict the behavior without an output schema.

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 description coverage is 100% and the only parameter, caseId, is already documented as 'Numeric test case ID to archive'. The tool description adds no additional parameter meaning beyond what the schema provides.

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 identifies the resource ('a test case') and the specific behavior ('Soft delete (archive)'). It also separates it from sibling deletion tools by emphasizing archiving and restoration.

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

Usage Guidelines3/5

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

The intended use case is implied: call this when you want to archive a test case, and the restoration note implies the operation is reversible. However, it does not explicitly mention alternatives or when not to use it, such as removing a case from a collection instead of deleting it.

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