Skip to main content
Glama
CipherNote MCP

CipherNote MCP

by xuns1919-ux

private_note_search

Search locally stored AES-256-GCM encrypted notes by query and return matching private note results with an optional limit.

Instructions

Search encrypted notes locally.

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": {
      "query": "<query>"
    },
    "name": "private_note_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

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

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

With no annotations supplied, the description carries the full disclosure burden and mostly fails it. 'Locally' and 'encrypted' hint that search runs on-device over encrypted content, but matching semantics, ranking, case sensitivity, whether decryption prompts are required, and result shape are all unstated.

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 sentence, front-loaded with the core action and no filler. Its brevity is efficient, though it shades into under-specification rather than true conciseness.

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?

A two-parameter search tool with no annotations and no output schema needs more than six words to be callable with confidence. Required usage context, match behavior, and result description are all absent.

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 should compensate for two undocumented parameters. It says nothing about what the query string matches or what limit controls, leaving only the self-evident parameter names and the schema's default/bounds to guide the agent.

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

Purpose3/5

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

States a recognizable verb (search) and resource (encrypted notes) plus a locality scope (locally), so the basic action is clear. However, it gives no distinguishing detail against siblings like private_note_recent or private_note_read, so an agent cannot tell from the description alone why it would pick this one.

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 when-to-use guidance at all: no mention of when to search versus listing recent notes (private_note_recent) or reading a specific note (private_note_read). The agent must infer the selection rule from sibling names, which the definition never references.

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