Skip to main content
Glama
BRO3886

Memory Custom

by BRO3886

delete_relations

Remove unwanted connections from a knowledge graph to maintain accurate data relationships. Specify entities and relation types to delete from your memory file.

Instructions

Delete multiple relations from the knowledge graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
relationsYesAn array of relations to delete
memoryFilePathYesThe path to the memory file

Implementation Reference

  • The core handler function in KnowledgeGraphManager that deletes specified relations by filtering them out from the graph's relations array and saving the updated graph to the memory file.
    async deleteRelations(
      relations: Relation[],
      filepath: string
    ): Promise<void> {
      await this.setMemoryFilePath(filepath);
      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 input schema definition for the delete_relations tool, specifying the expected parameters: an array of relations (each with from, to, relationType) and memoryFilePath.
    {
      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",
          },
          memoryFilePath: {
            type: "string",
            description: "The path to the memory file",
          },
        },
        required: ["relations", "memoryFilePath"],
      },
    },
  • index.ts:669-676 (registration)
    The registration in the CallToolRequestSchema switch statement that dispatches calls to the deleteRelations method and returns success message.
    case "delete_relations":
      await knowledgeGraphManager.deleteRelations(
        args.relations as Relation[],
        args.memoryFilePath as string
      );
      return {
        content: [{ type: "text", text: "Relations deleted successfully" }],
      };
  • Type definition for Relation used in delete_relations parameters.
    interface Relation {
      from: string;
      to: string;
      relationType: string;
    }
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 aspects like required permissions, whether deletions are reversible, error handling for non-existent relations, or batch operation limits. This leaves significant behavioral gaps for a destructive 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 any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent 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?

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It lacks essential context such as what happens after deletion (e.g., confirmation, error messages), side effects on the knowledge graph, or dependencies like required file formats for 'memoryFilePath'. This leaves the agent with insufficient information 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 schema description coverage is 100%, with clear documentation for both parameters ('relations' and 'memoryFilePath'). The description doesn't add any meaningful parameter semantics beyond what's already in the schema, such as format examples or constraints, so it meets the baseline for high schema coverage without providing extra value.

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 explicitly differentiate this tool from sibling tools like 'delete_entities' or 'delete_observations', 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 like 'delete_entities' or 'delete_observations'. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction beyond the basic purpose.

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/BRO3886/mcp-memory-custom'

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