Skip to main content
Glama
Sign In
Goodnotes Web MCP

Goodnotes Web MCP

by hb442
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

goodnotes_retry_rejected_step

Prepares a fresh retry only when the old receipt proves no mutation was sent, preserving receipt and attempt history; rejects uncertain, pending, or missing receipts before run_batch executes it.

Instructions

Prepare a fresh attempt only when the old receipt proves NO mutation was sent. Preserves the old receipt and attempt history. Rejects uncertain, pending or missing receipts; run_batch executes the prepared retry.

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": {
      "jobId": "<jobId>",
      "stepIndex": "<stepIndex>"
    },
    "name": "goodnotes_retry_rejected_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
stepIndexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.1

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses the critical safety behavior: the tool only prepares a retry when no mutation was sent, preserves the old receipt and attempt history, and rejects uncertain states. It also clarifies that this tool does not execute the retry; run_batch does.

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?

The description is three tight sentences, front-loaded with the precondition, and contains no redundant restatement. The handoff to run_batch is included concisely where it matters.

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?

The behavioral conditions are well covered, but with 0% schema description coverage and no output schema, the description leaves parameter meaning and the prepared-retry result unexplained. It is adequate for safe invocation but not fully complete.

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 the description never mentions jobId or stepIndex. It only indirectly implies a rejected step and an old receipt, adding little or no mapping or constraint meaning beyond the schema's field names and types.

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 ('Prepare a fresh attempt') and states the exact precondition: the old receipt must prove no mutation was sent. It also distinguishes preparation from execution by noting that run_batch executes the prepared retry, though it does not explicitly compare against skip_batch_step or other sibling tools.

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?

It gives a clear when-to-use condition and explicit when-not cases: uncertain, pending, or missing receipts are rejected. It also explains the follow-up path via run_batch, but it does not name an explicit alternative for skipping or inspecting the step.

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