Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

delete_product

Destructive

Moves a product and associated policies/licenses to Trash, making its licenses stop working immediately; can be restored within 30 days. Confirm with the user and state how many licenses are affected.

Instructions

Move a product to the Trash with its policies and licenses: those licenses stop working at once (validation answers as for an unknown key). It can be restored for 30 days with restore_from_trash. Confirm with the user first, saying how many licenses go with it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoproduct id, code or name; leave empty for every product

Output Schema

NameRequiredDescriptionDefault
noteYes
trashedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the supplied annotations (destructiveHint=true, idempotentHint=false) by disclosing the exact consequence: bundled licenses stop validating instantly, answering as for an unknown key. It also quantifies the reversibility window (30 days) and names the restoring tool, so the agent understands both the damage and the undo path before invoking.

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, each load-bearing: what is deleted, what happens to the license keys, and how to recover plus the confirmation requirement. The destructive consequence is front-loaded rather than buried, and there is no redundant restatement of the annotations.

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?

An output schema exists, so return values need no explanation, and with one fully documented parameter the remaining burden is behavioral. The description covers the cascade, the immediate license invalidation, the restore window, and the required user confirmation, which is everything an agent needs before calling a destructive tool.

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 single `product` parameter already documents accepting an id, code, or name, so the schema carries the parameter burden and baseline 3 applies. The description adds no syntax guidance and notably does not repeat the high-risk default that an empty value targets every product.

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?

Names a specific verb and resource ("Move a product to the Trash") and immediately scopes the blast radius with "with its policies and licenses", so an agent knows this is a cascading delete rather than a single-row removal. The sibling delete_license/delete_policy tools target sub-objects, and the explicit cascade wording makes the distinction clear.

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?

Gives the agent a concrete precondition ("Confirm with the user first, saying how many licenses go with it") and points at restore_from_trash as the recovery path with a 30-day window, which is exactly the when/when-not signal needed for a destructive tool. It stops short of routing to sibling alternatives such as delete_license when only some licenses should be removed.

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