Skip to main content
Glama
Sign In
Sticky Notes MCP Server

Sticky Notes MCP Server

by vedantparmar12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_notes

Delete every note in the sticky note file to erase all saved content. Confirmation is returned upon completion.

Instructions

Delete all notes from the sticky note file.

Returns:
    str: Confirmation message indicating the notes were deleted.

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": "delete_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the destructive action ('Delete all notes') and the return type (confirmation message), but it does not explicitly state permanence, non-reversibility, or any side effects like file modification. The behavior is clear but lacks extra context.

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 extremely concise: one sentence for the action plus a return spec. Every word is purposeful, and it is front-loaded with the main verb and resource. No wasted content.

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?

The tool is simple with no parameters and an output schema (implied by the return description). The description fully explains what the tool does and what it returns, leaving no ambiguity. Sibling tools do not require additional disambiguation for this straightforward delete operation.

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?

The tool has 0 parameters, so the baseline is 4. The description adds no parameter information because there are none. This is a perfect score for a parameterless tool.

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 clearly states the specific verb 'Delete' and resource 'all notes from the sticky note file', distinguishing it from sibling tools like add_note and read_notes. It is unambiguous and focused on a single, well-defined action.

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 intended use is implied by the description ('Delete all notes'), but there is no explicit guidance on when to use this tool instead of alternatives, nor any mention of exclusions or prerequisites. Context makes it obvious for deletion, but the description does not provide explicit usage scenarios or comparisons.

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