skim-pdf-mcp

Overview Schema Source Related Servers Discussions Admin

Clear processed underlines

clear_processed

DestructiveIdempotent

Permanently delete approved gray underlines by ID in an open Skim PDF; pending red underlines and highlights remain untouched.

Instructions

PERMANENTLY DELETE processed (gray) underlines by id. MODIFIES the Skim document.

Only run after the reader has explicitly approved clearing these ids. Deletes exactly the ids passed, and only if they are gray underlines: pending (red) underlines, highlights and other markup are skipped.

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": {
      "ids": "<ids>"
    },
    "name": "clear_processed"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Ids of gray underlines to delete.
`document_path`	No	Path of an open document. Default: the front document.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered; the description adds genuinely new behavior beyond them — permanent, irreversible deletion and a filtering rule that silently skips non-gray ids. It does not describe how skipped ids are reported back, keeping it at 4.

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?

Two short paragraphs with zero filler; the destructive nature and the precondition are both front-loaded before the detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, low-parameter mutation with full schema coverage, complete annotations, and an output schema, the description supplies everything else an agent needs: irreversibility, the approval precondition, and the id-filtering rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the ids are validated against gray-underline status and are the exact set deleted. It also clarifies document scope ('the Skim document') beyond the schema's default-to-front-document note.

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?

States a specific verb (PERMANENTLY DELETE) and resource (processed/gray underlines) with an explicit scope qualifier (by id) and notes it MODIFIES the Skim document. This cleanly separates it from read-only siblings like get_pending_underlines and the non-destructive mark_processed.

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?

Gives a clear precondition ('Only run after the reader has explicitly approved clearing these ids') and a when-not rule ('pending (red) underlines, highlights and other markup are skipped'). It does not explicitly route to a sibling alternative, so it falls just short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server