Skip to main content
Glama
Sign In
mcp-vault-reader

mcp-vault-reader

by LucasRocha179
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

memory_delete_note

Delete a note from the persistent memory vault by specifying its relative path. Use to remove outdated or incorrect entries.

Instructions

Deletes a note from the persistent memory vault.

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": {
      "path": "<path>"
    },
    "name": "memory_delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path of the note to delete (e.g., 'projects/old-app.md').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The description provides no annotations and adds no behavioral details beyond the basic action. It does not disclose whether deletion is permanent, whether related backlinks or index entries are affected, or any error conditions.

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?

A single, concise sentence that is front-loaded with the verb and object. No filler or redundant information, earning full marks.

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?

The tool has one parameter, no output schema, and no annotations. The description is minimally viable but lacks safety-critical context for a destructive operation, such as irreversibility or side effects, which feels incomplete for the task.

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 schema fully describes the 'path' parameter with a clear example, so the description adds no additional semantic value. Baseline of 3 applies since schema coverage is 100%.

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 'Deletes' with a clear object 'a note from the persistent memory vault'. It clearly distinguishes from sibling tools like memory_write_note (write) and memory_search (search), and the scope is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives, or any exclusions or prerequisites. The description simply states the action without context, leaving the agent to infer usage from the name and sibling set.

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