Skip to main content
Glama
Sign In
Sharpwave

Sharpwave

by Enlightened-Republic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

brain_supersede

Updates outdated memory nodes by replacing content, closing old edges, and adding a supersede link to preserve temporal integrity.

Instructions

Replace an outdated node with updated content. Closes old edges, writes a supersedes edge, preserving the memory graph's temporal integrity.

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": {
      "old_node_id": "<old_node_id>",
      "new_content": "<new_content>"
    },
    "name": "brain_supersede"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_labelNoUpdated label (defaults to old label)
new_contentYesUpdated content for the replacement node
old_node_idYesID of the node being superseded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Describes closing old edges and writing a supersedes edge, providing some behavioral context. However, without annotations, it misses disclosure on destructiveness, side effects, or whether the old node remains. No mention of permissions or rate limits.

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?

Single, well-structured sentence that front-loads the key action and consequence. No unnecessary words; every part earns its place.

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?

Covers core behavior for a graph update tool, but lacks return value information, reversibility, and whether the operation generates a new node ID. Adequate but with gaps given no output schema or annotations.

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?

Schema coverage is 100%, and the description adds context by explaining the role of each parameter in the supersede operation, e.g., 'old_node_id' and 'new_content' as updated content. 'new_label' defaults to old label, which is helpful.

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?

Clearly states the verb 'Replace' and resource 'outdated node', explaining the process of closing old edges and writing a supersedes edge to preserve temporal integrity. This distinguishes it from sibling tools like brain_write or brain_forget.

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?

Implies usage for updating content while maintaining history, but does not explicitly state when not to use or mention alternatives among siblings. Lacks guidance on prerequisites or context.

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