Gravity

Move a note to Deleted Notes

trash_note

DestructiveIdempotent

Move a note to Deleted Notes when the user asks to delete it. To clear a note off the list but keep it, use archive_note. restore_note brings it back until the user empties Deleted Notes; no tool deletes a note for good. Pass the revision you read: if the note changed since, Gravity keeps the newer text in a separate note. Without revision, the note is trashed as it is now. A note already in Deleted Notes stays there.

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

Input Schema

Name	Required	Description	Default
`note_id`	Yes	The note's ID (a UUID) from search, list_notes or fetch.
`revision`	No	The note's revision from fetch, list_notes or search. Leave out to trash the note as it is now.

Output Schema

Name	Required	Description	Default
`note`	Yes
`outcome`	Yes	unchanged: the note was already like that, so nothing was written.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context: deletion is reversible only until Deleted Notes is emptied, no tool performs permanent deletion, and an already-trashed note is left untouched (reinforcing idempotency). The revision-conflict behavior — newer text preserved in a separate note — is a genuinely non-obvious side effect disclosed here.

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?

Five short sentences, front-loaded with the action and the nearest alternative, each carrying a distinct fact (scope, alternative, undo, permanence, revision semantics, idempotency). No restatement of the title and no filler.

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 destructive two-parameter tool with an output schema, the definition covers reversibility, conflict handling, and repeat-invocation behavior — everything an agent needs to call it safely. Return values need not be described because an output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds consequence-level meaning the schema lacks: passing the revision you read protects against clobbering concurrent edits, whereas omitting it trashes the current state as-is. That converts a terse schema note into an actionable decision rule for the agent.

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 Deleted Notes') plus the user intent that triggers it ('when the user asks to delete it'). It explicitly distinguishes itself from archive_note and restore_note, so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('user asks to delete it'), names the alternative for the adjacent intent ('To clear a note off the list but keep it, use archive_note'), and covers the undo path via restore_note. It also rules out a non-existent hard-delete so the agent does not hunt for one.

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

All Gravity tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?