Skip to main content
Glama

Delete a note

delete_note
DestructiveIdempotent

Delete one note from your notebook.

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": {
      "notebook": "<notebook>",
      "key": "<key>"
    },
    "name": "delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesNote name, e.g. todo or project/status.
notebookYesSecret notebook token returned by create_notebook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description only adds that exactly one note is removed; it says nothing about whether deletion is permanent, what happens if the key does not exist, or whether the notebook token must be owned by the caller.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste. It is efficient, though for a destructive operation the brevity leaves it thin rather than richly informative.

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?

With full schema coverage and annotations carrying the destructive/idempotent profile, the essentials for invocation are present. What is missing is the consequence model: irreversibility and behavior on a missing note are the main things an agent would still need before calling a delete tool.

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 coverage is 100%, with both `key` and `notebook` documented including a pattern and an example note name, so the baseline of 3 applies. The description's phrase "from your notebook" loosely maps to the notebook parameter but adds no syntax or format detail beyond the schema.

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 gives a specific verb and resource ("Delete one note") and clarifies scope with "one" and "from your notebook", so an agent can tell it apart from read_notes and write_note. It stops short of explicitly naming a sibling or contrasting behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives such as write_note for overwriting, and no prerequisites or exclusions. The agent must infer that this is the removal path rather than the update path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.