Skip to main content
Glama
Sign In
Noteastic MCP

Noteastic MCP

by Canxinner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Noteastic-Notizbuch lesen

get_notebook

Retrieve metadata and a page overview for a notebook, including PDF backgrounds and handwritten elements, to support local inspection and comparison of Noteastic backups.

Instructions

Liefert Metadaten und eine Seitenübersicht eines Notizbuchs, einschließlich PDF-Hintergründen und handschriftlicher Elemente.

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": {
      "notebookId": "<notebookId>"
    },
    "name": "get_notebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
notebookIdYesID aus list_library oder search_library

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-like operation ('Liefert') and specifies what data is returned, including PDF backgrounds and handwritten elements. It does not explicitly state read-only behavior or error cases, but the phrasing and scope are sufficient for a simple one-parameter read 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 a single, focused sentence that leads with the action and object, then adds specific informative details. There is no filler, repetition, or unnecessary context.

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 tool with one required parameter and no output schema, the description provides enough information about what the agent will receive: metadata, page overview, PDF backgrounds, and handwritten elements. It could be more complete by explicitly stating that the operation is read-only, but overall it is adequate for selection and invocation.

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 notebookId is fully documented in the input schema with a description ('ID aus list_library oder search_library') and constraints. Since schema description coverage is 100%, the tool description does not need to add parameter details; the baseline of 3 applies.

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 action and resource: 'Liefert Metadaten und eine Seitenübersicht eines Notizbuchs' (provides metadata and a page overview of a notebook). It further distinguishes itself from siblings by explicitly mentioning PDF backgrounds and handwritten elements, which is a unique scope compared to get_page_assets or export_notebook.

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 usage context is only implied through the described output: if an agent needs notebook metadata or a page overview, this tool is appropriate. There is no explicit when-to-use/when-not-to-use guidance or mention of alternatives such as get_page_assets for individual page assets.

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