xgmem

delete_entities

Remove multiple entities and their associated relations from a project knowledge graph by specifying entity names.

Instructions

Delete multiple entities and their associated relations from the project 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": {
      "projectId": "<projectId>",
      "entityNames": "<entityNames>"
    },
    "name": "delete_entities"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes	The project identifier
`entityNames`	Yes	An array of entity names to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description adds value by disclosing that associated relations are also deleted (cascading behavior). However, it does not mention reversibility, permissions, or other side effects, leaving gaps for an AI agent.

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, concise sentence that conveys the core action without unnecessary words, effectively front-loading the purpose.

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?

For a deletion tool with no annotations or output schema, the description lacks important context such as irreversibility, confirmation requirements, or error conditions. It is too minimal for safe usage.

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 description coverage is 100% with clear parameter descriptions. The tool description adds no further parameter details, meeting the baseline but not exceeding it.

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 verb 'delete', the resource 'multiple entities', and includes the association with 'their associated relations', which distinguishes it from sibling tools like delete_relations or delete_observations.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or when-not conditions. For example, it doesn't mention if entities with relations should be deleted via this tool or if relations need to be removed first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server