Frostbyte

delete_release

DestructiveIdempotent

Permanently delete a release — requires confirm: true. Before calling, tell the user which release will be deleted and how many tasks it holds (list_tasks with releaseId and status "all"), and wait for an explicit yes in chat; never delete on your own initiative. Its tasks are kept and return to the Backlog, and its GitHub milestone is deleted.

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

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true, and only after the user has said yes in chat
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`projectId`	Yes	The project ID
`releaseId`	Yes	The release ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the destructive and non-read-only annotations, it discloses permanence, mandatory human confirmation, task preservation and relocation, and deletion of an external GitHub milestone. These details clarify both the data impact and the cross-system side effect, and they are consistent with openWorldHint and destructiveHint.

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 front-loads the permanent action and confirmation requirement, then presents the mandatory safety workflow and resulting side effects. Although the middle sentence is dense, every clause supports correct and safe invocation, with no filler or repetition.

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 destructive cross-system operation, it covers authorization, the required precheck, what is permanently removed, what survives, and the external milestone impact. Combined with the fully documented schema and annotations, this gives the agent everything material needed for safe invocation; the absence of an output schema is not a significant gap here.

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?

The schema already describes all four parameters, but the description adds operational meaning by connecting releaseId to the required list_tasks precheck and situating confirm within the full chat-approval workflow. It does not add guidance on obtaining or selecting projectId and releaseId, so it does not merit a 5.

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 uses a specific verb and resource: permanently deleting a release. It also distinguishes the operation from sibling deletion tools through its unique consequences: tasks return to the Backlog while the associated GitHub milestone is deleted.

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

Usage Guidelines5/5

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

It provides an explicit pre-call workflow: identify the release to the user, count its tasks using list_tasks with releaseId and status "all", and wait for an explicit yes. The instruction to never delete on the agent's own initiative clearly defines when the tool must not be used.

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

All Frostbyte tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?