Skip to main content
Glama
Sign In
Viwoods MCP

Viwoods MCP

by desyncc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

viwoods_list_notebooks

Read-onlyIdempotent

List shared Viwoods Paper-app notebooks, newest first, with page counts, writing pages, and last-changed times; filter by folder, title/folder words, or change dates.

Instructions

Shared notebooks in the Viwoods tablet's Paper app, newest first: id, title, folder, page count, which pages have writing (e.g. "1-3, 5") and when anything in it last changed. folder limits it to a folder and the folders under it. query keeps to notebooks whose title or folder holds every word of it (e.g. "recipes"), with no need for the handwriting index. since / until keep to notebooks with writing that changed in that time, and add pages_changed (which pages) to each; they take a date (2026-10-01, whole day), a date and time, today, yesterday, or how long ago (7d, 2w, 12h, 3m).

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

Input Schema

NameRequiredDescriptionDefault
queryNo
sinceNo
untilNo
folderNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is met elsewhere. The description adds genuinely behavioral facts: folder is recursive into subfolders, query matches every word against title or folder, and since/until alter the response by appending pages_changed.

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?

Dense but efficient; parameter behavior is front-loaded right after the resource statement and no sentence is filler. The leading enumeration of output fields is somewhat redundant given an output schema exists, slightly diluting the front-loading.

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

Completeness5/5

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

For a 4-param, zero-required filter tool this covers everything needed: all four filters, their interaction with the response, ordering, and time-format grammar. Return fields need not be re-explained since an output schema exists.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: folder recursion, query's AND-word matching on title/folder, and since/until accepting a date, date+time, 'today', 'yesterday', or relative durations (7d, 2w, 12h, 3m) with whole-day semantics for bare dates.

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?

States a specific verb (list) and resource (shared notebooks in the Viwoods Paper app) plus ordering (newest first) and the returned shape. The clause 'with no need for the handwriting index' implicitly separates it from viwoods_search_handwriting, so an agent can route between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains what each filter selects and when the since/until pair changes the output (adds pages_changed), which is real usage context. It stops short of naming alternatives explicitly (e.g. 'use search_handwriting for page content'), leaving that to inference.

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