Skip to main content
Glama
yodakeisuke

Knowledge Graph Memory Server

by yodakeisuke

delete_relations

Remove specified relationships between entities in the knowledge graph to maintain accurate data connections and eliminate outdated or incorrect associations.

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 updates. This is the exact implementation of the tool logic.
    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);
    }
  • index.ts:477-499 (registration)
    Registers the 'delete_relations' tool in the ListToolsRequestSchema handler, defining its 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"],
      },
    },
  • The dispatch case in CallToolRequestSchema handler that invokes the deleteRelations method on the manager instance.
    case "delete_relations":
      await knowledgeGraphManager.deleteRelations(args.relations as Relation[]);
      return createResponse("Relations deleted successfully");
  • TypeScript interface defining the structure of a Relation, used as input for the delete_relations tool.
    interface Relation {
      from: string;
      to: string;
      relationType: string;
    }
  • JSON schema defining the input structure for the delete_relations tool, specifying an array of relations with from, to, and relationType.
    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"],
    },
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. It states the action is 'Delete' (implying mutation/destruction) but lacks critical details: it doesn't specify if deletions are permanent, require specific permissions, have side effects (e.g., cascading deletions), or include error handling. This is a significant gap for a destructive 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 with zero waste. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place without redundancy.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens post-deletion (e.g., confirmation, error messages, or return values), behavioral constraints, or integration with sibling tools. The agent lacks sufficient context to use this tool safely and effectively.

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 'relations' parameter and its nested structure (from, to, relationType). The description adds no additional parameter semantics beyond implying multiple deletions via 'multiple relations'. Baseline 3 is appropriate as 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 purpose immediately understandable. It distinguishes from sibling tools like delete_entities and delete_observations by specifying the target resource type. However, it doesn't specify the exact scope or mechanism (e.g., batch deletion vs. individual), which prevents 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. It doesn't mention prerequisites (e.g., existing relations), exclusions (e.g., when not to delete), or comparisons with siblings like delete_entities or create_relations. The agent must infer usage from context 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/yodakeisuke/mcp-memory-domain-knowledge'

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