Skip to main content
Glama
CipherNote MCP

CipherNote MCP

by xuns1919-ux

private_note_delete

Permanently delete one private note by its note ID, removing locally stored encrypted content when the note is no longer needed.

Instructions

Permanently delete one note by ID.

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

Input Schema

NameRequiredDescriptionDefault
note_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only that deletion is permanent. It says nothing about what happens when the ID does not exist, whether the call is idempotent, what permissions are required, or whether any recovery is possible.

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?

A single front-loaded imperative with zero filler; the destructive qualifier is placed first where it matters. It is efficient but so short that brevity shades into under-specification.

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

Completeness2/5

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

For a destructive mutation with no annotations, no output schema, and an undocumented parameter, the definition leaves out the safety and failure-mode context an agent needs. 'Permanently' is the right note to strike but far from sufficient.

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 single parameter 'note_id' is documented nowhere beyond its type and length bounds. The phrase 'by ID' merely restates the parameter name and adds no format, source, or example for obtaining a valid ID.

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 names a specific verb and resource ('delete one note') plus the selector ('by ID'), and the word 'permanently' signals the operation is destructive rather than reversible. It does not explicitly distinguish itself from the nearby 'private_note_write' sibling, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus private_note_write, private_note_read, or the other siblings, and no preconditions such as confirming the note exists or that the caller owns it. The agent must infer the use case entirely from the name.

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