Skip to main content
Glama
Sign In
Mnemosyne MCP

Mnemosyne MCP

by zhadyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_observations

Delete specific observations from entities in a knowledge graph memory to remove outdated or incorrect facts.

Instructions

Delete specific observations from entities in your Memento MCP knowledge graph memory

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": {
      "deletions": "<deletions>"
    },
    "name": "delete_observations"
  }
}

Input Schema

NameRequiredDescriptionDefault
deletionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states the action and does not disclose irreversibility, required permissions, partial failure behavior, or return format. The description adds no behavioral insight beyond the basic 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 a single, front-loaded sentence with no superfluous words. It efficiently communicates the core function without redundancy.

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

Completeness2/5

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

This is a destructive mutation tool with no annotations and no output schema. The description fails to mention side effects, irreversibility, prerequisites, or the exact parameter structure. The description is too minimal to fully support confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter 'deletions' with 0% top-level description coverage. The tool description hints at entities and observations, but it does not explain the array-of-objects structure or the required fields entityName and observations. The description provides minimal compensatory value for the schema gap.

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 ('Delete') and the target ('specific observations from entities'), making it distinct from sibling tools like delete_entities and delete_relations. It precisely identifies the resource and operation.

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?

The description provides no guidance on when to use this tool versus alternatives such as add_observations or delete_entities. It lacks context about prerequisites, exclusions, or conditions where this tool is preferred.

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