Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

delete_policy

Destructive

Move a licensing policy to Trash so its issued licenses stop working immediately; restore it within 30 days if needed.

Instructions

Move a policy to the Trash with the licenses issued from it: they stop working at once. 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

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": {
      "policy": "<policy>"
    },
    "name": "delete_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYespolicy id or name
productNoproduct id, code or name, when the policy name exists in several products

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?

The annotations already flag destructiveHint=true, but the description adds the consequences that matter: issued licenses 'stop working at once' and the object is recoverable for exactly 30 days via restore_from_trash. It also imposes a human-confirmation gate with a specific message requirement, which is behavioral guidance no annotation encodes.

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, zero filler, with the destructive effect and cascade front-loaded before the recovery path and the confirmation instruction. Every clause carries operational information an agent must act on.

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 two-parameter tool with an output schema present, the description covers the risk profile, cascade side effects, reversibility window, and the required confirmation step. Nothing an agent needs in order to invoke this safely is missing.

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%, so both `policy` (id or name) and `product` (disambiguator when the name exists in several products) are already documented in the schema. The description adds no parameter-level detail beyond that — notably it never mentions the `product` disambiguation, which is the one case where an agent could delete the wrong policy. Baseline 3 applies.

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 opens with a specific verb and resource ('Move a policy to the Trash') and immediately discloses the cascade scope ('with the licenses issued from it'), which is exactly what distinguishes this from delete_license or delete_product. It also names the sibling it is not (restore_from_trash), so an agent can route correctly without opening a schema.

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?

It gives an explicit prerequisite — 'Confirm with the user first, saying how many licenses go with it' — and names restore_from_trash as the recovery path, which implies when this is the right vs. wrong call. It stops short of stating when not to delete at all (e.g., update_policy as a softer alternative), so it is clear context rather than a full when/when-not decision tree.

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