Skip to main content
Glama
Sign In
Sharpwave

Sharpwave

by Enlightened-Republic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

brain_forget

Remove a node from memory, optionally forcing deletion of connected edges.

Instructions

Physically delete a node from the brain. Refuses to delete nodes with active edges unless force=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": {
      "node_id": "<node_id>"
    },
    "name": "brain_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoIf true, also drops active edges (default false)
node_idYesID of the node to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that deletion is physical and that the tool refuses to delete nodes with active edges unless force=true. This gives important behavioral context, though it could mention additional side effects or permissions.

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 a single sentence, front-loading the action. It is concise and contains no extraneous information.

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?

Given the tool's simplicity (2 params, no output schema, no annotations), the description covers the core functionality and edge case (active edges). Missing details like error handling or response format, but overall adequate.

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 parameters described. The description adds minimal extra meaning, merely reinforcing the force parameter's behavior from the schema. No significant new information beyond the schema.

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 action ('Physically delete a node') and the specific resource (the brain node). It also adds a behavioral nuance about active edges, which helps distinguish it from other sibling tools like brain_link.

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 description does not explicitly explain when to use this tool vs alternatives like brain_supersede or brain_write. It implies usage for node deletion but lacks guidance on which tool to choose for related tasks.

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