Gravity

Archive a note

archive_note

Idempotent

Take a note off the list into Archive, for something done or no longer needed in view but worth keeping. Nothing is deleted, and search still finds it. When the user asks to delete a note, use trash_note instead. rescue_note brings it back to the top of the list. An archived note stays archived; a note in Deleted Notes returns an error.

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

Input Schema

Name	Required	Description	Default
`note_id`	Yes	The note's ID (a UUID) from search, list_notes or fetch.

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

Behavior5/5

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

The annotations already declare non-destructive, idempotent, non-readOnly, but the description adds substantive context beyond them: nothing is deleted, search still surfaces archived notes, and archiving is sticky ("stays archived"). It also discloses the one error condition, which the annotations cannot express.

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?

Four short sentences, each carrying distinct information: effect, reversibility/visibility, sibling routing, and error condition. The primary definition is front-loaded before the alternatives.

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?

An output schema exists, so return values need not be explained, and the single input is schema-documented. What remains for a state-changing tool — reversibility, discoverability after archiving, alternatives, and failure mode — is all covered.

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 and schema coverage is 100%, so the schema already fully documents note_id including its UUID format and where to obtain it. The description adds no further meaning about the parameter, which is the expected baseline here.

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?

"Take a note off the list into Archive" names a specific verb (archive) and resource (note) plus the scope of the effect, and the description immediately separates it from trash_note and rescue_note. An agent can tell what this does and what it does not do without opening any 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?

It gives explicit routing: when the user asks to delete, use trash_note instead; rescue_note is the inverse operation. It also names a precondition failure case (a note in Deleted Notes returns an error), which tells the agent when this call is not valid.

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?