M00N Report MCP

Official

Overview Schema Source Related Servers Discussions(1)Admin

delete_release

DestructiveIdempotent

Archive a release to remove it from active use while retaining test collections and launches. Restore later through the interface.

Instructions

Soft delete (archive) a release. The release can be restored via the UI. All linked Test Collections and launches are preserved.

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": {
      "releaseId": "<releaseId>"
    },
    "name": "delete_release"
  }
}

Input Schema

Name	Required	Description	Default
`releaseId`	Yes	Release UUID to archive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Aug 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: the deletion is soft, restoration is possible through the UI, and linked Test Collections and launches are preserved. This is exactly the kind of non-obvious behavior an agent needs to know and is not captured in the structured annotation fields.

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?

Three short sentences deliver all essential information with no redundancy or filler. The primary action is front-loaded, and subsequent sentences provide valuable non-obvious details.

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 single-parameter, no-output-schema tool, the description is complete. It states the action, the restoration path, and the preservation of related resources, giving an agent enough to invoke it correctly without missing important consequences.

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?

The input schema already documents releaseId as 'Release UUID to archive' with 100% coverage. The description adds little beyond the schema, but it is consistent with the parameter's meaning. Given full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Soft delete (archive) a release.' It immediately distinguishes this tool from sibling delete tools by naming the target resource and clarifying the action is a soft delete/archive rather than a permanent purge.

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 a clear context for when to use the tool: when you need to archive a release. It also indirectly sets expectations by noting restoration is done via the UI, implying this is not a permanent delete. It does not explicitly name alternatives, but the resource-specific purpose makes the usage context sufficiently clear.

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

Deploy Server