Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_compare_exports

Read-only

Compare two PDF snapshots within bounded page ranges by page position and extracted text, optionally checking rendered appearance, and return differences without modifying documents.

Instructions

Compare two PDF snapshots by page position, extracted text and optionally rendered appearance. Bounded page ranges; returns differences without modifying documents.

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": {
      "leftExportId": "<leftExportId>",
      "rightExportId": "<rightExportId>"
    },
    "name": "goodnotes_compare_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
visualNo
maxPagesNo
startPageNo
leftExportIdYes
rightExportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real context beyond them: comparison is bounded to page ranges (explaining the maxPages default of 10) and the output is a set of differences rather than a mutation. It does not describe result structure or cost of visual rendering, keeping it below a 5.

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?

Two tightly written sentences with zero waste. The core purpose leads, and the scoping/return behavior follows immediately.

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?

With no output schema and 0% parameter documentation, the description should say more about what a 'difference' record contains and how pages beyond maxPages are handled. It is adequate to call the tool but leaves the result format and the export-ID semantics to the schema.

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 carry all parameter meaning. It partially does: 'bounded page ranges' maps to startPage/maxPages and 'optionally rendered appearance' maps to visual, but leftExportId/rightExportId are never characterized (UUID export references) and the 10-page default cap is not restated.

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?

States a specific verb (compare) and resource (two PDF snapshots/exports) and names the comparison axes: page position, extracted text, and optional rendered appearance. This clearly separates it from siblings like goodnotes_combine_pdf or goodnotes_export, though no sibling is named 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?

Implied when-to-use is clear from 'compare two PDF snapshots', and the visual flag is framed as optional. However, there is no explicit guidance on when to choose this over other inspection paths (e.g. goodnotes_inspect) or any stated prerequisites such as both exports already existing.

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