Viwoods MCP

Overview Schema Source Related Servers Discussions Admin

viwoods_add_pdf_notebook

Imports a PDF from your PC to a Viwoods tablet as a new Paper notebook for handwriting, placing it in a shared top-level folder or the top level when writing is enabled.

Instructions

Put a PDF from this PC on the Viwoods tablet as a new Paper notebook to write on, into a shared top level folder (or the top level). Only when the user has switched writing on.

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": {
      "pdf_path": "<pdf_path>",
      "title": "<title>"
    },
    "name": "viwoods_add_pdf_notebook"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`folder`	No
`pdf_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations cannot express: the source is a local PC file and the operation requires the tablet's writing mode to be enabled. It omits failure behavior (folder missing, title collision), which keeps it below 5.

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 front-loaded sentence with the action first, then destination, then precondition. The parenthetical '(or the top level)' and 'to write on' add mild redundancy but every clause carries real information.

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?

An output schema exists, so return values need no explanation here. For a 3-parameter write operation, the description covers source, destination, and the enabling precondition; only edge-case behavior (existing folder, duplicate titles, invalid path) is left unstated.

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 all three parameters. It clarifies `folder` semantics (shared top-level, or top level when omitted, matching default "") and identifies `pdf_path` as a file from this PC, but says nothing about `title` beyond implying the notebook's name.

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 and resource chain: put a PC PDF onto the Viwoods tablet as a new Paper notebook. The action is unmistakably distinct from siblings like viwoods_list_notebooks or viwoods_read_pages, so an agent can route to it without opening the schema.

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?

Gives a clear precondition ('Only when the user has switched writing on') that gates invocation, which is more than most definitions offer. It does not name alternatives or say what to do when the gate is not met, so it falls short of a full when/when-not/alternative statement.

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

Deploy Server