Skip to main content
Glama
Sign In
Knowledge MCP

Knowledge MCP

by jihoho12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_node

Remove a knowledge node from the graph, with an option to also delete connected edges.

Instructions

노드를 삭제(soft delete)합니다.

Args: name: 삭제할 노드 이름 cascade: True면 연결된 edge도 함께 삭제. False면 edge가 있을 경우 거부.

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": {
      "name": "<name>"
    },
    "name": "delete_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
cascadeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Discloses soft delete behavior and cascade parameter effects. With no annotations, the description carries the full burden and adequately covers key behavioral traits.

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?

Extremely concise: two sentences and parameter docs. Front-loaded with the main action, no wasted words.

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?

Given the presence of an output schema and sibling context, the description is mostly complete. It could mention error cases (e.g., node not found), but covers the core behavior well.

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?

With 0% schema coverage, the description adds meaning to both parameters: name (the node to delete) and cascade (behavior when edges exist). This compensates for the lack of schema descriptions.

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 it deletes a node with soft delete, distinguishing it from siblings like delete_edge (edge deletion) and update_node (modification). However, it does not explicitly contrast itself with other siblings.

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 guidance on when to use this tool versus alternatives (e.g., merge_nodes or update_node). The description lacks context for decision-making.

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