Skip to main content
Glama
Sign In
annotate-mcp

annotate-mcp

by ElaineMHr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

annotate_clear

Remove annotations permanently from a page. Provide specific mark IDs to delete selected items, or leave empty to clear all marks.

Instructions

Delete marks permanently. With no ids, deletes everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "annotate_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoSpecific mark ids. Omit to clear all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must bear the full burden. It discloses permanence ('permanently') and the dangerous bulk behavior ('with no ids, deletes everything'), which is critical for a delete operation. It does not mention auth or undo, but the key risks are covered.

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 concise sentences with no fluff. The first sentence states the action, and the second clarifies the critical edge case. Excellent front-loading.

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?

Given the tool's simplicity (one optional param, no output schema), the description fully covers its purpose, behavior, and the critical default case. No missing information that would impede correct invocation.

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?

The single 'ids' parameter is already fully described in the schema ('Specific mark ids. Omit to clear all.'), so schema coverage is 100%. The tool description adds no extra parameter semantics beyond what the schema provides, so baseline 3 applies.

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 uses a specific verb ('Delete') and resource ('marks'), and clearly distinguishes behavior when ids are provided versus omitted. This differentiates it from sibling tools like annotate_list or annotate_resolve.

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 provides clear context on how to use the tool: provide ids for specific marks, omit ids to clear all. It does not explicitly name alternatives or exclusions, but the parameter guidance is sufficient for typical use.

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