Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

trash_note

Move a note to the trash or leave a shared note's share; items can be restored and are permanently removed after 30 days.

Instructions

Move a note to the trash (restore_note brings it back; the trash empties itself after 30 days). On a note shared with the user, this leaves the share instead.

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": {
      "id": "<id>"
    },
    "name": "trash_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, correctly framing this as a reversible mutation. The description adds real value beyond that: reversibility via restore_note, a 30-day retention window, and that shared notes cause the user to leave the share. However it doesn't state permissions needed or what the call returns (e.g., the trashed note), so with annotations carrying the safety profile a middle score fits.

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 compact sentences, each carrying distinct information: reversibility and retention first, then the shared-note edge case. No filler or repetition.

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 single-parameter reversible mutation with annotations covering the safety profile, the description covers the key concerns: recovery path, retention period, and side effect on shared notes. Only the return value is left unexplained, but that is minor here.

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?

Only one parameter (id), and schema description coverage is 0%, so the description could have clarified that id is the note identifier. Since the lone param is self-evidently the target note, this is a modest gap rather than a serious one.

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: "Move a note to the trash." It implicitly distinguishes itself from restore_note by naming the inverse operation, so an agent can tell the two apart without opening a 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?

Names the sibling restore_note as the reversal path and explains the 30-day auto-purge, which gives clear context for when this action is appropriate. It stops short of explicit exclusions (e.g., permanent deletion vs. this soft delete), but the context is unambiguous.

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