Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_unlock_object

Unlock a prepared native sticky note, text box, image, or shape position/size lock, then verify unchanged content, view, appearance, and native unlocked state after reload.

Instructions

Unlock a prepared native sticky, text box, image or shape position/size lock. Checks unchanged content/view, appearance and native unlocked state after reload.

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": {
      "unlockId": "<unlockId>",
      "operationId": "<operationId>"
    },
    "name": "goodnotes_unlock_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
unlockIdYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish the write-shaped profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-obvious context: the tool verifies unchanged content/view, appearance, and native unlocked state after reload. It still omits what happens on verification failure, whether the operation is idempotent, and what the openWorldHint implies about remote state.

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?

Two compact sentences, with the action and supported object types front-loaded and the verification behaviour following. Phrasing is terse to the point of terseness ('position/size lock', 'unchanged content/view'), but nothing is 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?

There is no output schema, so the description is the only place to state what a successful unlock returns and how a failed post-reload verification surfaces. It also fails to explain how to obtain the required unlockId, leaving an agent unable to construct a valid call from this definition 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 neither parameter is described. The description does not say that unlockId is the handle returned by the prepare step, nor what operationId is for (presumably an idempotency/dedupe key) or the constraints of its pattern. Two required, cryptically named parameters are left entirely to inference.

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 uses a specific verb ('Unlock') plus the resource and enumerates supported object types (native sticky, text box, image, shape) and the lock kinds (position/size). It is clear what the tool does, but it does not disambiguate against the sibling goodnotes_unlock_sticky, which appears to overlap with the 'native sticky' case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'prepared' hints that a prepare step must precede the call, but the prerequisite (goodnotes_prepare_unlock) is never named and no when-to-use/when-not guidance is given. With goodnotes_unlock_sticky in the sibling list, an agent has no stated rule for choosing between them.

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