trash_fileMove an exact NotePom file to trash.
| Name | Required | Description | Default |
|---|---|---|---|
| fileId | Yes | ||
| idempotencyKey | Yes | ||
| expectedUpdatedAt | No |
| Name | Required | Description | Default |
|---|---|---|---|
| trashed | Yes | ||
| trashEntryId | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, so the description only needs to add nuance. It adds that the file is moved to trash (not permanently purged) and targets an exact file, but it doesn't mention concurrency behavior via expectedUpdatedAt or what happens on missing files. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one clean sentence with no filler, and the action and object are front-loaded. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The core action is clear, and annotations plus an output schema cover safety and return values. However, for a destructive operation requiring an idempotency key, the description leaves usage and parameter semantics under-specified, though the explicit schema property names partially compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate by explaining the parameters; it doesn't. fileId, idempotencyKey, and expectedUpdatedAt are never mentioned, leaving the roles of the idempotency key and optimistic-concurrency field entirely to inference.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb ('Move'), resource ('an exact NotePom file'), and destination ('to trash'), so an agent can tell it is a targeted file-level trash operation. It doesn't explicitly contrast with siblings like trash_workspace_item or move_file, which prevents a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to choose this tool over trash_workspace_item, move_file, restore_trash_entry, or purge_trash_entry. The word 'exact' implies an identity-based file operation, but no conditions, exclusions, or alternative routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, and lifecycle pairs like publish_note_listing vs publish_media_listing or get_note vs get_collaboration_note are separated by clear wording. A few near-pairs such as move_file vs move_workspace_item and trash_file vs trash_workspace_item could still cause an agent to pick the wrong tool without careful reading.
All 38 tools follow one consistent verb_noun snake_case pattern with no camelCase or mixed conventions. Even less common verbs like upsert, trash, purge, and validate are applied uniformly, making the tool set predictable.
38 tools is well above the 25+ threshold and makes the overall surface feel heavy for tool selection. The number is defensible given the broad workspace, collaboration, and marketplace scope, but as a single MCP server it is not especially well-scoped.
The tool set covers workspace content lifecycle, collaboration, public pages, marketplace listings, Stripe seller flow, and agent registration without major dead ends. Minor gaps exist, such as no permanent delete outside of the trash flow and no direct collaboration-note deletion, but core workflows are supported.