Skip to main content
Glama
CipherNote MCP

CipherNote MCP

by xuns1919-ux

private_note_read

Retrieve and decrypt one encrypted note by ID to securely read locally stored content.

Instructions

Read one encrypted 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_read"
  }
}

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.9/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. It mentions the note is 'encrypted' but does not say whether the response is decrypted plaintext or ciphertext, whether decryption requires special permissions or key access, or what happens for a missing or unauthorized ID — meaningful gaps for a read whose defining trait is encryption.

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?

One short, front-loaded sentence with no filler or redundancy. The efficiency is appropriate, though the same brevity is the source of the tool's missing context.

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 one-parameter read with no annotations and no output schema, the definition is minimally sufficient but leaves the return value ambiguous — an agent cannot tell whether it receives decrypted text, encrypted bytes, or metadata, which matters given the explicit 'encrypted' framing.

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?

The single parameter has 0% schema description coverage — the schema only constrains it to a 1-128 character string. The description contributes that this string is a note identifier used for single-record lookup, which is modest but real added meaning over a bare 'note_id: string'.

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 — 'Read one encrypted note' — and the 'by ID' qualifier scopes it to single-record lookup. This lets an agent distinguish it from the sibling 'private_note_search' and 'private_note_recent' without needing an explicit exclusion, though it never names 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The 'by ID' phrasing weakly implies it is for retrieval when an identifier is already known, but the description never says to prefer search or recent when only a query or timeframe is available.

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