Skip to main content
Glama

get_trash

Read-onlyIdempotent

Lo que está en la papelera: documentos, canvases, recaps, clips y entidades del Atlas que se borraron y todavía se pueden recuperar con restore_from_trash.

Cada ítem trae `tipo` (document | canvas | meeting | clip | entity), `id`,
`nombre` y cuándo se borró. Las entidades fusionadas no aparecen: no se
borraron, se absorbieron en otra. Sin workspace_id mira todos a la vez.

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

Input Schema

NameRequiredDescriptionDefault
tipoNoSólo de este tipo
limitNoMáximo (default: 50)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes beyond them by disclosing a non-obvious rule: merged entities never show up in trash because they were absorbed rather than deleted. It also states the scope expansion when workspace_id is omitted, which is real behavioral context an agent could otherwise get wrong.

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?

The content is front-loaded, with the resource first, then the returned fields, then the edge case about merged entities and the workspace scoping. Nearly every sentence earns its place, though the field enumeration partially duplicates what the caller will see in the results anyway.

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?

There is no output schema, so the description's list of returned fields (tipo, id, nombre, deletion date) carries the burden and does so adequately. Combined with the annotation profile and the merged-entity caveat, an agent has enough to call this correctly; only the response ordering or pagination behavior is left unstated.

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 tipo, limit, and workspace_id are already documented with their enums and bounds. The description only reinforces the workspace_id default ('Sin workspace_id mira todos a la vez'), adding no new syntax or format meaning beyond the schema, so the baseline of 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 starts with a specific resource ('lo que está en la papelera') and enumerates exactly which object kinds appear (documentos, canvases, recaps, clips, entidades del Atlas). It also names the sibling tool restore_from_trash as the recovery path, so the agent can tell a listing operation apart from a restore operation without opening either 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 clearly frames the use case (see what was deleted but is still recoverable) and explicitly names restore_from_trash as the follow-up action. It does not spell out when to prefer this over non-trash listing tools such as get_all_files or get_documents, so the guidance is clear but not exhaustive.

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