Skip to main content
Glama

delete_nodes

Remove multiple nodes and their connected edges from the MemoryMesh knowledge graph by specifying node names to streamline graph management and maintain data integrity.

Instructions

Delete multiple nodes and their associated edges from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNamesYesAn array of node names to delete

Implementation Reference

  • The handler logic for the 'delete_nodes' tool in GraphToolHandler.handleTool switch statement. It delegates deletion to knowledgeGraphManager and returns a formatted response confirming the action.
    case "delete_nodes":
        await this.knowledgeGraphManager.deleteNodes(args.nodeNames);
        return formatToolResponse({
            actionTaken: `Deleted nodes: ${args.nodeNames.join(', ')}`
        });
  • The tool definition including name, description, and input schema for validating arguments to the 'delete_nodes' tool.
    {
        name: "delete_nodes",
        description: "Delete multiple nodes and their associated edges from the knowledge graph",
        inputSchema: {
            type: "object",
            properties: {
                nodeNames: {
                    type: "array",
                    items: {type: "string", description: "Node name to delete"},
                    description: "An array of node names to delete"
                },
            },
            required: ["nodeNames"],
        },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions deletion of nodes and associated edges, implying a destructive operation, but lacks details on permissions needed, whether deletions are reversible, error handling, or side effects like cascading impacts. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given the tool's complexity as a destructive operation with no annotations and no output schema, the description is inadequate. It doesn't explain what happens upon deletion (e.g., confirmation, return values, or error messages), leaving critical behavioral aspects undocumented for safe and effective use.

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 input schema has 100% description coverage, clearly documenting the 'nodeNames' parameter as an array of node names to delete. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete multiple nodes') and the resource ('knowledge graph'), with the additional detail about associated edges being removed. It distinguishes from sibling tools like 'delete_edges' by specifying nodes as the primary target, though it doesn't explicitly contrast with other delete operations like 'delete_artifact' or 'delete_location'.

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. With many sibling tools for deleting specific types (e.g., 'delete_artifact', 'delete_location'), it doesn't clarify if this is for generic nodes or if there are prerequisites, exclusions, or recommended contexts for its use.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CheMiguel23/MemoryMesh'

If you have feedback or need assistance with the MCP directory API, please join our Discord server