Skip to main content
Glama
Sign In
Noteastic MCP

Noteastic MCP

by Canxinner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Noteastic-Bibliothek auflisten

list_library

Retrieve the complete folder and notebook hierarchy from a Noteastic backup, so you can inspect and compare backup contents.

Instructions

Liest die vollständige Ordner- und Notizbuchhierarchie aus der Sicherung.

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": "list_library"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly discloses that the operation is read-only ('Liest') and scoped to the complete folder/notebook hierarchy from the backup. It does not mention ordering, pagination, or result format, but those are minor for a zero-parameter listing tool.

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 with no filler. It states the action and the resource immediately, making it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter read tool, the description adequately conveys the source and scope of the returned data. However, with no output schema, a brief mention of the expected shape or format of the returned hierarchy would make it fully complete.

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

Parameters4/5

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

The input schema has no properties and there are zero parameters, so there is nothing for the description to add. This matches the baseline for a zero-parameter tool.

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 names a clear verb ('Liest') and resource ('vollständige Ordner- und Notizbuchhierarchie aus der Sicherung'), so an agent knows this tool returns the full hierarchy. It does not explicitly distinguish itself from siblings such as search_library or get_notebook, though the 'vollständige Hierarchie' phrasing implies a broad listing.

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?

No explicit when-to-use or when-not-to-use guidance is provided, and no alternative tools are mentioned. The agent must infer from the name and description that this is for retrieving the complete hierarchy, but the choice versus search_library or get_notebook is not spelled out.

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

Deploy Server

Other Tools