Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_draw_connector

Draw straight lines or arrows as native ink strokes on a Goodnotes canvas using the current pen style, with start and end points set as canvas fractions.

Instructions

Draw a straight line or arrow as native ink strokes using the current pen style. Endpoints are canvas fractions. This is drawn ink, not a connector that follows moved objects.

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>",
      "from": "<from>",
      "to": "<to>",
      "operationId": "<operationId>"
    },
    "name": "goodnotes_draw_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
arrowNo
viewIdYes
inkStyleNo
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so the description's added value is the claim that output is baked ink strokes rather than a persistent attached connector, plus that styling comes from the current pen. That is genuine behavioral context beyond the annotations, though it omits undo/idempotency behavior around operationId.

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?

Three short sentences, front-loaded with the action and artifact, then the coordinate convention, then the disambiguation. No filler or restatement of the 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 mutating tool with six parameters, nested inkStyle, and no output schema, the description covers the core artifact and coordinate system but leaves the return value, failure modes, and the meaning of operationId and arrow unaddressed. Adequate but with clear gaps.

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 compensate. It does add crucial meaning for from/to ('canvas fractions'), which the schema only exposes as bare numeric bounds, but it says nothing about arrow, inkStyle fields, viewId, or the role of operationId, leaving most of the six parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Draw a straight line or arrow as native ink strokes') and immediately distinguishes the behavior from a live connector. An agent can tell exactly what artifact this produces without opening the schema.

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 negation 'not a connector that follows moved objects' clarifies the intended artifact, which implicitly tells the agent when this is the right choice. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g. any object-creation or connector-style sibling) to route between.

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