Skip to main content
Glama
Sign In
memory-mcp

memory-mcp

by palimpsest-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_entities

Remove multiple entities and their related connections from the knowledge graph in one operation.

Instructions

Delete multiple entities and their associated relations from the knowledge graph.

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": {
      "entityNames": "<entityNames>"
    },
    "name": "delete_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityNamesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the destructive action and the cascading deletion of associated relations, but does not mention irreversibility, partial failures, or whether observations are affected. This is moderate but not exhaustive.

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 unnecessary words. It efficiently conveys purpose and scope, making it highly concise and well-structured.

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 is simple with one parameter and an output schema, so return values need not be explained. However, the description leaves ambiguity about the effect on observations and lacks error-handling or prerequisite details. It is adequate but not comprehensive.

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 only parameter, entityNames, is not explicitly described, but the phrase 'multiple entities' directly maps to it. Since schema coverage is 0%, the description compensates somewhat, but it adds no details about matching behavior or constraints beyond what the schema shows.

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), the resource (entities), and the scope (multiple entities and their associated relations). It distinguishes from sibling tools like delete_observations and delete_relations by focusing on entities and cascading relation deletion.

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 implies usage for deleting entities but does not explicitly mention when not to use it or compare with alternatives like delete_relations. Sibling names are present, but no direct guidance is given.

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