Skip to main content
Glama
itseasy21

Knowledge Graph Memory Server

delete_relations

Remove specified connections between entities in the knowledge graph to maintain accurate relationship data.

Instructions

Delete multiple relations from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relationsYesAn array of relations to delete

Implementation Reference

  • The core handler function in KnowledgeGraphManager that deletes the specified relations by filtering them out from the loaded graph and saving the changes to the memory file.
    async deleteRelations(relations: Relation[]): 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);
    }
  • JSON Schema defining the input structure for the delete_relations tool, specifying an array of relations with from, to, and relationType fields.
    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"],
    },
  • index.ts:526-528 (registration)
    Registers the handler for the delete_relations tool in the CallToolRequestHandler switch statement, dispatching calls to KnowledgeGraphManager.deleteRelations.
    case "delete_relations":
      await knowledgeGraphManager.deleteRelations(args.relations as Relation[]);
      return { content: [{ type: "text", text: "Relations deleted successfully" }] };
  • index.ts:397-419 (registration)
    Tool registration in the ListToolsRequestHandler, including name, description, and input schema.
    {
      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"],
      },
    },
  • TypeScript interface defining the structure of a Relation object used by the delete_relations tool.
    interface Relation {
      from: string;
      to: string;
      relationType: string;
      createdAt: string;
      version: number;
    }
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. It states the tool deletes relations, implying a destructive mutation, but fails to mention critical details like permissions needed, whether deletions are permanent or reversible, error handling for invalid inputs, or any rate limits. This leaves significant gaps for a mutation tool.

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 is front-loaded with the key action and resource, making it highly concise and well-structured for quick understanding.

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 insufficiently complete. It lacks details on behavioral traits (e.g., side effects, error responses), usage context relative to siblings, and output expectations, leaving the agent with significant uncertainty about how to invoke it correctly.

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 (from, to, relationType). The description adds no additional semantic context beyond implying bulk deletion, so it meets the baseline score of 3 where the schema handles parameter documentation effectively.

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 target resource ('multiple relations from the knowledge graph'), which distinguishes it from sibling tools like delete_entities or delete_observations. However, it doesn't specify what constitutes a 'relation' beyond what's implied by the sibling tools, making it slightly less specific than a perfect score.

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 update_relations. It lacks context about prerequisites, such as whether relations must exist or be deletable, and offers no explicit exclusions or recommendations for sibling tools.

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/itseasy21/mcp-knowledge-graph'

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