Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_preview

Read-only

Capture the current document viewport as one image when you need to verify visual positioning or placement.

Instructions

Return one image of the current document viewport, only when visual positioning is needed.

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": {
      "viewId": "<viewId>"
    },
    "name": "goodnotes_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds that exactly one image of the current viewport is captured, which is meaningful scoping behavior, but it says nothing about image format, resolution, latency, or the cost of repeated calls in an open-world context.

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?

A single tight sentence with the action front-loaded and the usage constraint second. Nothing is padded or redundant.

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

Completeness2/5

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

With no output schema, the description must convey what comes back; 'one image' is the bare minimum and leaves format and framing unresolved. The undocumented required parameter is also a completeness gap, making this under-specified despite the tool's apparent simplicity.

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?

There is exactly one required parameter, viewId, and schema description coverage is 0%, so the description is the only place its meaning could be explained — yet it never mentions viewId at all. An agent gets no hint about what a viewId identifies, how to obtain one, or what happens with an invalid one.

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 gives a specific verb and resource: return one image of the current document viewport. It implicitly distinguishes itself from whole-document tools like goodnotes_export or goodnotes_inspect by scoping to the 'viewport', but it does not name or contrast any sibling explicitly.

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 clause 'only when visual positioning is needed' sets a genuine when-to-use condition, which is more than most descriptions offer. However, it is qualitative and names no alternative (e.g. inspect, find_objects) for when textual data suffices, nor any exclusion cases.

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