Skip to main content
Glama
Sign In
Kybase

Kybase

by Kyrzin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

restore_note

Restores a soft-deleted note from the trash by UUID. Fails if the note was never deleted, already restored, purged, or a live note now holds the same title.

Instructions

Undo delete_note: brings a soft-deleted note back. Errors if the note isn't in the trash (never deleted, already restored, or purged past the retention window), or if a live note has since taken the same title (rename one of them first, then retry).

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
idYesUUID of a note currently in the trash — the same id delete_note was given

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • addedInput schema / properties / id / description
      Added value: +"UUID of a note currently in the trash — the same id delete_note was given"
    • removedInput schema / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses soft-delete semantics, a retention window past which restore fails, and a title-collision failure mode with a fix. It omits permissions/auth needs and what is returned on success, so it is strong but not exhaustive.

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 sentences, front-loaded with the inverse-of-delete framing, then a dense list of failure conditions and their fixes. Every clause carries information.

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?

Preconditions, error states, and remediation are covered thoroughly for a one-parameter mutation. The only gap is that with no output schema it leaves the success return value unstated.

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% and the single id parameter is already documented as the trash UUID also passed to delete_note, so the schema does the heavy lifting. The description adds no format or constraint information about the id beyond that baseline.

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 ('Undo delete_note: brings a soft-deleted note back') and explicitly ties itself to the delete_note sibling, making the inverse relationship unmistakable among the many note tools.

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?

The 'Undo delete_note' framing makes the when-to-use case clear, and it gives explicit remediation for the title-collision case ('rename one of them first, then retry'). It stops short of stating alternatives for notes that were never soft-deleted, though those are handled as error cases.

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

Deploy Server

Other Tools