Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_verify_restored_page

Read-only

Independently verify a restored notebook page against its saved deletion checkpoint by checking exact native identities, order, and full PDF content baseline without altering the original receipt.

Instructions

Independently verify a page restoration against its saved deletion checkpoint: exact native identities/order and full PDF content baseline. Does not repeat recovery or change the original receipt.

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": {
      "deleteOperationId": "<deleteOperationId>"
    },
    "name": "goodnotes_verify_restored_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
deleteOperationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A3.7/5.0
Behavior3/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 usefully adds that the original receipt is unchanged and recovery is not re-run. It says nothing about what a failed verification returns or how discrepancies are reported, which matters for a verification tool with no output schema.

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 tight sentences with the verification target front-loaded and the non-behavioral caveat second. No filler or restatement of the tool name.

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 verification tool with no output schema, the description should say what the result looks like (pass/fail, discrepancy list) and what happens on failure. It covers what is compared and the read-only nature but leaves the outcome contract 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 coverage is 0% for the single parameter, so the description must carry the burden. Mentioning 'saved deletion checkpoint' usefully implies that deleteOperationId identifies that checkpoint, but it never explains the ID's format, origin, or where to obtain it.

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 ('verify') and resource ('page restoration') and names exactly what is checked: native identities/order and full PDF content baseline. The clause 'Does not repeat recovery' implicitly distinguishes it from the restore_page sibling, though no alternative is named outright.

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?

'Independently verify a page restoration against its saved deletion checkpoint' establishes the post-restore verification context clearly, and 'Does not repeat recovery' supplies a when-not boundary. It stops short of naming the tool to use when the user actually wants to perform or redo a restore.

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