Skip to main content
Glama
Sign In
Knowledge MCP

Knowledge MCP

by jihoho12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_edge

Remove unwanted edges from your knowledge graph by specifying an edge ID or filtering by source, target, and relation.

Instructions

edge를 삭제(soft delete)합니다. edge_id로 직접 삭제하거나, source/target/relation 조건으로 삭제합니다.

Args: edge_id: 삭제할 edge ID (이 값이 있으면 다른 조건 무시) source: source 노드 이름 (조건 삭제용) target: target 노드 이름 (조건 삭제용) relation: 관계 타입 (조건 삭제용)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_edge"
  }
}

Input Schema

NameRequiredDescriptionDefault
edge_idNo
sourceNo
targetNo
relationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided. Description only mentions 'soft delete' without explaining implications (e.g., reversibility, logging). No disclosure of side effects, idempotency, or error behavior.

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?

Two concise sentences plus bulleted args. No fluff. Front-loaded with purpose.

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

Completeness3/5

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

Covers main functionality and param relationships. Lacks detail on output schema, behavior when no match, or handling multiple matches. Output schema exists but not referenced.

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

Parameters4/5

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

Adds meaning beyond schema: explains edge_id overrides other params, and source/target/relation are for conditional deletion. Schema coverage is 0%, so description compensates well.

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?

Description clearly states it deletes edges (soft delete) and specifies two modes: by edge_id or by source/target/relation conditions. Distinguishes from sibling tool delete_node by focusing on edges.

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?

No explicit guidance on when to use direct vs conditional deletion, nor when not to use. Does not mention prerequisites or alternative tools.

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