Skip to main content
Glama

delete_edges

Remove specific edges from a knowledge graph using an array of edge identifiers, including source, target, and edge type, within the MemoryMesh MCP server framework.

Instructions

Delete multiple edges from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edgesYesArray of edges to delete

Implementation Reference

  • The handler function executes the tool logic by deleting the specified edges using the knowledge graph manager and returns a formatted success response.
    case "delete_edges":
        await this.knowledgeGraphManager.deleteEdges(args.edges);
        return formatToolResponse({
            actionTaken: "Deleted edges from knowledge graph"
        });
  • Defines the tool's metadata, description, and input schema which requires an array of edge objects each specifying from, to, and edgeType.
    {
        name: "delete_edges",
        description: "Delete multiple edges from the knowledge graph",
        inputSchema: {
            type: "object",
            properties: {
                edges: {
                    type: "array",
                    description: "Array of edges to delete",
                    items: {
                        type: "object",
                        description: "Edge to delete",
                        properties: {
                            from: {type: "string", description: "The name of the node where the edge starts"},
                            to: {type: "string", description: "The name of the node where the edge ends"},
                            edgeType: {type: "string", description: "The type of the edge"},
                        },
                        required: ["from", "to", "edgeType"],
                    },
                },
            },
            required: ["edges"],
        },
    },
  • Registers all static tools from allStaticTools (including delete_edges) into the central ToolsRegistry map for discovery and handling.
    // Register static tools
    allStaticTools.forEach(tool => {
        this.tools.set(tool.name, tool);
    });
  • Routes tool calls matching graph operations (including delete_edges) to the GraphToolHandler instance.
    if (toolName.match(/^(add|update|delete)_(nodes|edges)$/)) {
        return this.graphHandler;
  • Entry point for tool execution: retrieves the appropriate handler via factory and invokes its handleTool method.
    const handler = ToolHandlerFactory.getHandler(name);
    return await handler.handleTool(name, args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, it doesn't specify whether this is reversible, what permissions are required, what happens to connected data, or error handling for non-existent edges. The description lacks crucial behavioral context for a destructive 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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and understandable without unnecessary elaboration.

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 destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, what the tool returns, error conditions, or important behavioral constraints. Given the complexity of graph operations and lack of structured safety information, more context is needed.

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%, so the schema fully documents the 'edges' parameter structure. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain edge format expectations, validation rules, or deletion behavior specifics. Baseline 3 is appropriate when schema does all the work.

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') and resource ('multiple edges from the knowledge graph'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_nodes' or 'delete_artifact' by specifying edges, but doesn't explicitly contrast with 'update_edges' or other edge-related tools.

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 like 'update_edges' or other deletion tools. It doesn't mention prerequisites, consequences, or typical scenarios for edge deletion versus other operations.

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