Skip to main content
Glama
Sign In
mcp-knowledge-base

mcp-knowledge-base

by vishnu-vasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_note

Remove a note from the knowledge base by its ID. Returns true if the note was deleted, false if it was not found.

Instructions

Delete a note by ID.

Args: note_id: The ID of the note to delete.

Returns: True if the note was deleted, False if not found.

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

Input Schema

NameRequiredDescriptionDefault
note_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

The description discloses the return behavior (True if deleted, False if not found), which is useful. However, with no annotations, it omits details about permanence, permissions, or side effects—important context for a destructive operation.

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 very concise, with a one-line purpose and clear Args/Returns sections. Every sentence earns its place, and no unnecessary detail is included.

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

Completeness4/5

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

For a simple single-parameter delete operation, the description covers the purpose, parameter role, and return behavior. The output schema is indicated to exist, so return value handling is adequate. No significant gaps remain.

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 schema only declares note_id as an integer, but the description explains it as 'The ID of the note to delete,' adding meaningful semantics. This compensates for the 0% schema description coverage, though the explanation is minimal.

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 the specific verb 'Delete' and identifies the resource as 'note' with a clear method ('by ID'). This unambiguously distinguishes it from sibling tools like update_note or delete_task.

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 usage is implied: use when you have a note ID to delete. However, the description does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or prerequisites.

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