Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

restore_note

Recovers a deleted Anchor note from the trash by its ID, so you can return mistakenly removed content without recreating it.

Instructions

Bring a note back from the trash.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already state that this is not read-only, not destructive, and not open-world. The description adds the useful behavioral detail that the note is being restored specifically from the trash, but it does not explain permissions, idempotency, failure behavior, or where the note is restored to.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short, front-loaded sentence with no wasted wording. It is concise and readable, though its brevity contributes to the missing operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter restore operation with annotations and no output schema, the description covers the core action and source state. It remains incomplete regarding the required identifier semantics and what happens after restoration or when the note is not in the trash.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to compensate for the single undocumented 'id' parameter. It only says 'a note', which weakly implies that an identifier is needed, but does not explain the expected ID format or meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: bringing a note back from the trash. It is easy to understand what operation is performed. However, it does not distinguish this tool from nearby alternatives such as restore_note_version or trash_note.

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

Usage Guidelines3/5

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

The phrase 'from the trash' implies the condition under which this tool should be used: the note must already be in the trash. There is no explicit guidance about alternatives, prerequisites, or what to do if the note is not trashed.

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