Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_plan_study_collection

Plan study cards and figures into bounded, linked boards with measured geometry, preserved captions and source pages, and previews before writing supplied explanations and exercises.

Instructions

Plan up to 240 source-based cards and 120 original figures into bounded, linked boards. Measures real text/figure geometry, preserves figure-caption groups and source pages, produces previews before writing. The caller supplies explanations and exercises.

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": {
      "collectionId": "<collectionId>",
      "materials": "<materials>"
    },
    "name": "goodnotes_plan_study_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitsNo
materialsYes
collectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool measures real geometry, preserves figure-caption groups and source pages, and generates previews before writing. That is useful behavioral context for a non-destructive write operation, though permissions and side effects are not described.

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?

The description is three sentences with the core purpose front-loaded and no obvious repetition. Some phrasing such as 'bounded, linked boards' is compact but not fully self-explanatory.

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?

For a complex nested write tool with no output schema and no schema descriptions, the definition is only partially complete. It conveys the high-level workflow and preview behavior but leaves important parameter shapes and limits for the caller to infer from the schema alone.

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

Parameters2/5

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

Schema description coverage is 0% and the schema is deeply nested, so the description carries the full burden. It only mentions card/figure counts and that the caller supplies explanations and exercises; it does not explain collectionId, materials structure, limits, layout, crop, span, pages, or section semantics.

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 states a specific action and resource: planning source-based cards and figures into linked boards. It implies a planning/preview stage distinct from execution tools, but it does not explicitly name a sibling or explain the boundary with prepare/review/run.

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?

Usage is implied by 'produces previews before writing' and by the note that the caller supplies explanations and exercises. However, there is no explicit when-to-use guidance, prerequisites, or comparison to sibling planning tools.

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