Skip to main content
Glama

delete_relations

Remove specified relationships between entities from the knowledge graph to maintain accurate semantic connections in code indexing systems.

Instructions

Delete multiple relations from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relationsYesAn array of relations to delete

Implementation Reference

  • The primary handler for the 'delete_relations' tool. Validates the input arguments and calls the knowledge graph manager to delete the specified relations.
    export const deleteRelationsHandler: ToolHandler = async (args) => {
      if (!args.relations || !Array.isArray(args.relations)) {
        throw new Error("The 'relations' parameter is required and must be an array");
      }
    
      // Valider chaque relation
      for (const relation of args.relations) {
        if (!relation.from || typeof relation.from !== 'string') {
          throw new Error("Each relation must have a 'from' string property");
        }
        if (!relation.to || typeof relation.to !== 'string') {
          throw new Error("Each relation must have a 'to' string property");
        }
        if (!relation.relationType || typeof relation.relationType !== 'string') {
          throw new Error("Each relation must have a 'relationType' string property");
        }
      }
    
      try {
        await knowledgeGraphManager.deleteRelations(args.relations);
        return { 
          content: [{ 
            type: "text", 
            text: "Relations deleted successfully" 
          }] 
        };
      } catch (error) {
        console.error("Error in delete_relations tool:", error);
        throw error;
      }
    };
  • Input schema definition for the 'delete_relations' tool, specifying the structure of the 'relations' array parameter.
    export const deleteRelationsTool: ToolDefinition = {
      name: "delete_relations",
      description: "Delete multiple relations from the knowledge graph",
      inputSchema: {
        type: "object",
        properties: {
          relations: {
            type: "array",
            items: {
              type: "object",
              properties: {
                from: { 
                  type: "string", 
                  description: "The name of the entity where the relation starts" 
                },
                to: { 
                  type: "string", 
                  description: "The name of the entity where the relation ends" 
                },
                relationType: { 
                  type: "string", 
                  description: "The type of the relation" 
                },
              },
              required: ["from", "to", "relationType"],
            },
            description: "An array of relations to delete"
          },
        },
        required: ["relations"],
      },
    };
  • Core helper method in KnowledgeGraphManager that performs the actual deletion of relations from the in-memory graph and persists to file.
    async deleteRelations(relations: RelationInput[]): Promise<void> {
      const graph = await this.loadGraph();
      graph.relations = graph.relations.filter(r => !relations.some(delRelation => 
        r.from === delRelation.from &&
        r.to === delRelation.to &&
        r.relationType === delRelation.relationType
      ));
      await this.saveGraph(graph);
    }
  • The getExpectedTools function lists 'delete_relations' among the expected tools for verification after auto-registration.
    export function getExpectedTools(): string[] {
      return [
        // Outils Graph (9 outils)
        'create_entities',
        'create_relations',
        'add_observations',
        'delete_entities',
        'delete_observations',
        'delete_relations',
        'read_graph',
        'search_nodes',
        'open_nodes',
    
        // Outils RAG (5 outils - avec injection_rag comme outil principal)
        'injection_rag',      // Nouvel outil principal
        'index_project',      // Alias déprécié (rétrocompatibilité)
        'search_code',
        'manage_projects',
        'update_project'
      ];
    }
  • Alternative inline handler logic for 'delete_relations' in the combined graph tools executor switch statement.
    case "delete_relations":
        await knowledgeGraphManager.deleteRelations(args.relations);
        return { content: [{ type: "text", text: "Relations deleted successfully" }] };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, it doesn't specify whether this operation is reversible, what permissions are required, how errors are handled, or what happens to related data. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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 purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place in conveying the core functionality.

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 incomplete. It doesn't explain what happens after deletion, whether there are side effects, what the return value looks like, or any error conditions. Given the complexity and risk of a delete operation, more contextual information 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%, with the schema fully documenting the 'relations' array parameter and its nested properties. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 relations from the knowledge graph'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_entities' or 'delete_observations' beyond specifying 'relations' as the target resource.

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 'delete_entities' or 'delete_observations'. It lacks context about prerequisites, when-not-to-use scenarios, or explicit comparisons with sibling tools, leaving the agent to infer usage from tool names alone.

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

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/ali-48/rag-mcp-server'

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