Skip to main content
Glama
Sign In
memory-mcp

memory-mcp

by jmars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_relations

Remove one or more relations from a knowledge graph by specifying source, target, and relation type. Omit relation type to delete all connections between two entities.

Instructions

Delete multiple relations from the knowledge graph.

Each relation must have: from (str), to (str), relationType (str). If relationType is omitted, all relations between from and to are deleted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "relations": "<relations>"
    },
    "name": "delete_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
relationsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the transparency burden. It discloses a key behavioral nuance: if relationType is omitted, all relations between from and to are deleted. It also specifies required fields. However, it does not mention error handling, reversibility, or side effects on associated entities.

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 two-sentence description is efficient: the first declares the core action, the second specifies requirements and the optional-relationType behavior. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with one array parameter, the description covers the essential behavior and the critical nuance about relationType. It relies on the existing output schema for return values. It could elaborate on error behavior or atomicity, but it is sufficiently complete for basic selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines a 'relations' array with no inner structure (0% coverage). The description compensates by specifying each relation must have from (str), to (str), and relationType (str), and clarifies the effect of omitting relationType. This fully disambiguates the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Delete multiple relations from the knowledge graph' with a specific verb and resource, and distinguishes from sibling delete tools (delete_entities, delete_observations) by explicitly targeting relations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for deleting relations, but does not explicitly provide guidance on when to use it versus alternatives or when not to use it. The mention of multiple relations and the optional relationType provides some context but lacks exclusions or alternative tool references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools