Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_create_text

Creates an editable text box at a specified empty canvas point, refusing non-empty fields and verifying exact persistence after reload so text edits stay reliable.

Instructions

Create an editable text box at an empty canvas point. Refuses an existing non-empty text field; checks exact persistence 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": {
      "viewId": "<viewId>",
      "x": "<x>",
      "y": "<y>",
      "text": "<text>",
      "operationId": "<operationId>"
    },
    "name": "goodnotes_create_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYes
viewIdYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations it discloses a concrete failure mode (rejects a non-empty text field) and a post-condition (persistence is verified after reload), which tells the agent the call may fail and that the write is durable. It omits permission/auth needs and any rate or size constraints.

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 short sentences, front-loaded with the action and followed by the behavioral caveat; no filler. It is dense enough to be slightly cryptic, particularly the reload-check clause.

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?

For a five-parameter write tool with no output schema and no parameter descriptions, the definition leaves key calling information unexplained: coordinate normalization, the operationId contract, text length limits, and what a refusal looks like. The behavioral note is helpful but the definition is not complete enough to call reliably without inspecting the schema.

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% across five required parameters, including operationId and the normalized x/y bounds, and the description supplies no meaning for any of them. 'Empty canvas point' only faintly gestures at x/y without explaining the 0.02–0.98/0.08–0.92 normalization or the idempotency role of operationId.

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 ('Create an editable text box') plus the placement condition ('at an empty canvas point'), which clearly separates it from edit/read/write text siblings. It stops short of naming which sibling to use when the target isn't an empty point.

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?

'at an empty canvas point' and 'Refuses an existing non-empty text field' imply when the tool applies and when it will fail. No alternatives (goodnotes_edit_text, goodnotes_write_text, goodnotes_create_object) are named, so routing is left to inference.

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