Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

list_trash

Read-onlyIdempotent

Lists deleted products, policies, licenses, and customers in Trash, including related items and days remaining before permanent deletion.

Instructions

List what is in the Trash (deleted products, policies, licenses and customers the member may see), with what went with each and the days left before it is deleted for good.

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": "list_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower, yet the description still adds real context: results are permission-scoped ('the member may see'), each entry includes related dependents ('what went with each'), and a retention countdown is surfaced. It does not mention pagination or ordering, which is a minor residual gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler, and the core action ('List what is in the Trash') is front-loaded. The nested parenthetical and 'what went with each' phrasing make it slightly harder to parse than necessary, but nothing is redundant.

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 zero-parameter read tool with rich annotations and an output schema, the description covers everything an agent needs: scope, permission-based filtering, what each entry contains, and the retention/deletion horizon. Return-value detail is correctly left to the output schema.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the schema baseline of 4 applies. The description correctly implies a no-argument listing call with filtering applied implicitly by member permissions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (list) and resource (Trash), and enumerates the item types returned (deleted products, policies, licenses, customers), which implicitly separates it from the plain list_* siblings. It stops short of explicitly naming restore_from_trash as the paired action, so the differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for inspecting deleted items, and the mention of 'days left before it is deleted for good' hints at a pre-restore check. There is no explicit when-to-use statement and no pointer to restore_from_trash as the follow-up action.

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