Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

restore_from_trash

Restore a deleted item and its associated licenses from Trash so they validate again; if the parent item is still in Trash, restore that first.

Instructions

Restore a deleted item with everything that was deleted with it; its licenses validate again within seconds. Fails while something it belongs to is still in the Trash (restore that first).

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": {
      "item": "<item>"
    },
    "name": "restore_from_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesthe id from list_trash, or the deleted item's name (a license by the start of its key)

Output Schema

NameRequiredDescriptionDefault
restoredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the cascading restore of dependent objects, the fact that licenses revalidate within seconds, and a specific failure mode tied to parent objects. The annotations already flag non-readOnly and non-idempotent; the description adds the operational consequences an agent needs.

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?

Two tight sentences with zero filler: the cascade behavior leads, followed by the failure precondition. Every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with an output schema and full annotation coverage, the description covers scope, side effects, and the blocking precondition. Only a note on what the restore response or error looks like is missing, which the output schema largely covers.

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 parameter already documents that it accepts an id from list_trash or a deleted item's name/key prefix. The description adds no further meaning about the argument, so the 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?

States a specific verb and resource ('Restore a deleted item') and, crucially, the cascade scope ('with everything that was deleted with it'). The reference to 'the id from list_trash' implicitly separates it from the sibling that only lists trash contents.

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 a concrete precondition and ordering rule: it fails while a parent object is still in the Trash, and that parent must be restored first. It does not name an alternative restore path, but the when-to-use context is clear enough to act on.

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