Skip to main content
Glama

Deleted-item recovery

spur_manage_trash
Destructive

List deleted records or restore a property, owner, or list. Permanent deletion and empty-trash require explicit confirmation.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only say destructiveHint=true and readOnlyHint=false for the tool as a whole, which is coarse for a tool mixing a safe list with irrecoverable operations. The description adds real value by scoping destructiveness to permanent deletion and empty-trash and flagging that both require explicit confirmation. It doesn't cover edge behavior such as restore conflicts or whether empty is account-wide and irreversible.

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 sentences, zero filler. The capability list comes first and the safety constraint is front-loaded as the second sentence where it matters most.

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

Completeness3/5

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

For a four-action tool with irrecoverable operations, no output schema, and confirmation gating, the definition is thin on consequences: what list returns, whether empty wipes everything or only expired items, and whether restore can fail. The schema covers parameters well, but the description leaves meaningful behavioral questions unanswered.

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 oneOf variants, enums, and confirm semantics are fully documented in the schema, so the schema carries the weight. The description restates the action and type values ('property, owner, or list') without adding format, ID semantics, or scoping detail beyond the schema. Baseline 3 is appropriate.

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 names the resource (deleted records) and enumerates the concrete operations: listing, restoring a property/owner/list, permanent deletion, and empty-trash. An agent can tell what the tool does without opening the schema. It stops short of naming a 5 because it does not distinguish itself from siblings like spur_manage_property_list or spur_manage_owner, which an agent might reach for by name alone.

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 implied by 'deleted records or restore' — use this when content has been deleted and needs viewing or recovery. The confirmation precondition for permanent deletion and empty-trash is stated, which is useful context. However, there is no explicit when-not guidance or named alternative for non-deleted-record management.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources