Skip to main content
Glama
CipherNote MCP

CipherNote MCP

by xuns1919-ux

private_note_write

Create encrypted local notes with titles, content, tags, and importance for private long-term storage; do not use for passwords, tokens, or other credentials.

Instructions

Write an encrypted local note. Do not use it for passwords, tokens, or other credentials.

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "private_note_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleYes
contentYes
importanceNo

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.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the note is local and encrypted and excludes credential storage, but it does not explain whether writes overwrite existing notes, require permissions or keys, return anything, or fail in particular ways.

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 short sentences, front-loaded with the core action and followed by a critical safety exclusion. There is no filler and every sentence carries useful information.

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 write tool with four undocumented parameters, no annotations, and no output schema, the description is incomplete. It omits parameter semantics, mutation behavior, and return information, leaving the agent without enough context to invoke it confidently.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no meaning for any of the four parameters. It does not explain what title, content, tags, or importance do, so it fails to compensate for the absent schema descriptions.

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 specific verb and resource: "Write an encrypted local note." An agent can distinguish this write operation from the read, search, recent, and delete siblings by the verb, though the description does not explicitly name those alternatives.

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?

It implies use for notes and gives a clear prohibition against passwords, tokens, and credentials. However, it offers no explicit guidance on when to use this write tool versus private_note_search, private_note_read, or other siblings, and no prerequisites are stated.

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