knowledge-library-mcp

list_permanent_notes

List all permanent notes in a knowledge library area to review and manage your saved knowledge.

Instructions

List all permanent notes within one area.

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": {
      "area": "<area>"
    },
    "name": "list_permanent_notes"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'List all' clearly indicates a read-only, exhaustive listing, but it does not explain how 'within one area' is interpreted (e.g., exact match, hierarchical inclusion), whether results are sorted, or any pagination behavior.

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?

The description is one short, front-loaded sentence that directly states the action and scope. Every word contributes meaning, and there is no redundant or filler content.

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?

The tool is simple and has an output schema, so return-value documentation is not required. However, the description is missing useful context about how to obtain a valid 'area' value and how this tool relates to list_areas, leaving an agent to infer that connection from sibling names.

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?

Schema description coverage is 0%, so the description must compensate for the single required 'area' parameter. It partially does by tying 'area' to the scope of the listing, but it does not explain what values area accepts, where they come from (e.g., list_areas), or the expected format.

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

Purpose5/5

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

The description states a specific verb ('List'), a specific resource ('permanent notes'), and a clear scope ('within one area'). It differentiates from siblings such as list_areas (which lists areas) and search_notes (which searches notes) by emphasizing 'all permanent notes' within a single area.

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 description implies the use case: when you need all permanent notes in one area. However, it provides no explicit guidance about when to prefer this tool over alternatives like search_notes, nor does it mention when not to use it.

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

Deploy Server