Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_run_study_revision

Run a saved revision step that rechecks original content, style, and appearance, rejects occupied destinations, verifies persistence and unchanged surroundings, then exports a final preview.

Instructions

Run one saved revision step. Rechecks exact original content/style/appearance, rejects occupied visible destinations, verifies native persistence and unchanged visible surroundings. Never automatically repeats uncertain writes. Exports a final preview.

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": {
      "revisionId": "<revisionId>"
    },
    "name": "goodnotes_run_study_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by describing the internal verification sequence, the rejection of occupied destinations, and the export of a final preview. 'Never automatically repeats uncertain writes' is especially valuable for an agent deciding whether to retry after an ambiguous outcome. It still doesn't say what is returned on rejection or how failure is signaled.

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?

Five short clauses, front-loaded with the action and followed by the behavioral guarantees in descending importance. No filler sentences, and each clause carries a distinct constraint.

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?

For a one-parameter mutation tool with no output schema, the description covers safety posture (non-repeating writes, destination rejection), verification behavior, and the side effect of exporting a preview. Only the failure/return signaling is left unspecified.

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%, but there is only one parameter and the schema itself constrains it to a UUID pattern. The description adds meaning by tying 'revisionId' to a previously saved revision step rather than an arbitrary identifier, though it does not state what happens if the ID is unknown or stale.

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 and resource ('Run one saved revision step') and immediately qualifies it with execution semantics that separate it from planning/preparation steps named in the sibling set. It never explicitly names a sibling, so differentiation is inferred rather than declared.

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 word 'saved' implies a revision must already exist (planned/prepared elsewhere), and 'Run' implies execution rather than review or status checks. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains implied.

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