Gravity

Restore a note

restore_note

Idempotent

Take a note out of Deleted Notes when the user wants it back. It returns to where it was: its old place in the list, or Archive if it was archived. It doesn't move to the top; call rescue_note after for that. Find deleted notes with list_notes and state deleted. A note that isn't in Deleted Notes stays as it is.

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": "restore_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.5/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing where the note lands (its old list position, or Archive if it was archived) and the no-op case ('A note that isn't in Deleted Notes stays as it is'), which corroborates idempotentHint=true. The remaining gap is minor: no mention of failure modes or permission requirements, though destructiveHint=false and readOnlyHint=false already frame this as a safe, reversible mutation.

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?

Front-loaded with purpose, then placement behavior, then the sibling alternative, then how to find candidates, then the edge case. Every sentence carries distinct information with no restatement of the name or title.

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 single-parameter, idempotent restore operation with an output schema available, the description covers intent, outcome, alternatives, discovery, and the non-deleted edge case. An agent has everything needed to call it correctly.

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 coverage is 100% with a single required note_id already documented as a UUID obtainable from search, list_notes or fetch. The description adds no further parameter meaning, 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?

States a concrete verb+resource ('Take a note out of Deleted Notes') and scopes it to the user's intent ('when the user wants it back'). It also implicitly distinguishes itself from rescue_note by explaining that it does not move the note to the top.

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?

Explicit when-to-use is given, plus the alternative: 'call rescue_note after for that' when the note should go to the top. It also names the discovery path ('Find deleted notes with list_notes and state deleted') so the agent knows how to obtain a valid note_id before calling.

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?