Skip to main content
Glama
CipherNote MCP

CipherNote MCP

by xuns1919-ux

private_note_recent

List recent private note metadata without returning note bodies, with an optional limit of up to 20. Use it to review note activity while keeping note content private.

Instructions

List recent note metadata without returning note bodies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "private_note_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It usefully discloses the output boundary (metadata only, no bodies) but says nothing about what 'recent' means, ordering, pagination behavior, or any permission requirements for private notes.

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 sentence, front-loaded with the operation and immediately followed by the key output constraint. No filler, though the terseness leaves the gaps noted in other dimensions.

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 simple, parameter-light read tool with no output schema, the description covers the essential contract (metadata, not bodies). It is still incomplete regarding how 'recent' is defined, how many items come back by default, and what metadata fields are included.

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% for the single 'limit' parameter, so the description is the only place semantics could be added — and it mentions nothing about limiting results, the default of 5, or the 1-20 range. The word 'recent' gestures at result count but does not explain the parameter.

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 gives a specific verb and resource ('List recent note metadata') plus a scope boundary ('without returning note bodies'), which cleanly separates it from private_note_read. It stops short of naming a sibling, but the operation is unambiguous.

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?

The exclusion of note bodies implicitly signals that private_note_read is the tool to use when content is needed, and 'recent' implies a recency-ordered listing. However, there is no explicit when-to-use guidance versus private_note_search, and no statement about when this listing is preferable.

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