Skip to main content
Glama
Sign In
Engram

Engram

by rwnalds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

brain_delete

Permanently delete a note from the vault (recoverable via git history) to eliminate incorrect or duplicated information.

Instructions

Delete a note (recoverable via git history). Prefer brain_move into an archive folder — deleting destroys the reasoning trail, archiving only removes it from search. Delete when the note is wrong or duplicated, archive when it is merely no longer true.

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

Input Schema

NameRequiredDescriptionDefault
pathYesvault-relative path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5
  2. Removedv0.1.2
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that deletion is recoverable via git history, that it destroys the reasoning trail, and contrasts with archiving's effect on search. It does not mention permissions or side effects on linked notes, but for a simple delete operation this is substantial transparency.

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 sentences, front-loaded with the primary action, then concise guidance. Every clause earns its place, with no fluff or repetition.

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 (one parameter, no output schema), and the description covers the purpose, recoverability, and decision framework for use verses archiving. It is complete enough for an agent to select and invoke the tool correctly.

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 the 'path' parameter already described as 'vault-relative path'. The description does not add any additional parameter semantics, but there is no need to compensate given the schema's clarity.

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 opens with 'Delete a note', a specific verb and resource, and immediately distinguishes itself from brain_move by stating the preferred alternative. It clearly identifies the tool's core function.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'Prefer brain_move into an archive folder' and gives precise criteria: 'Delete when the note is wrong or duplicated, archive when it is merely no longer true.' This directly addresses when to use this tool vs alternatives.

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