personal-kg-mcp

Overview Schema Source Related Servers Discussions Admin

kg_update_node

Modify an existing knowledge node's content, tags, importance, or visibility. Partial updates change only the fields you specify.

Instructions

Updates an existing knowledge node. Use to modify content, tags, importance, or visibility of a node. Supports partial updates - only specified fields are changed.

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

Input Schema

Name	Required	Description
`id`	Yes	ID of the node to update
`tags`	No	Replace all tags with this array
`content`	No	Replace the node's content entirely
`mergeTags`	No	Add these tags to existing tags (set union)
`importance`	No	Update importance level
`removeTags`	No	Remove these specific tags
`visibility`	No	Update visibility level
`appendContent`	No	Append text to the existing content

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It usefully discloses that updates are partial ('only specified fields are changed'), which is valuable behavioral context. Yet it says nothing about permissions, reversibility, return values, or failure modes—important gaps for a mutation 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?

Two sentences, front-loaded with the core action and supported fields. Every word serves a purpose, and the partial-update clarification earns its place. This is appropriately concise.

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 tool's moderate complexity (8 params, no annotations, no output schema), the description plus the fully described schema is largely complete. It states what the tool does, what can be changed, and the partial-update behavior. A mention of response/error behavior or permissions would make it fully complete.

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 input schema already describes all 8 parameters, so schema description coverage is 100%, which sets a baseline of 3. The description adds only the general partial-update note, not field-specific meaning, so it neither improves nor harms 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 opens with 'Updates an existing knowledge node,' clearly identifying the specific verb and resource. It also enumerates the editable fields (content, tags, importance, visibility) and notes partial-update support, which distinguishes it from sibling tools like kg_capture or kg_node.

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

Usage Guidelines4/5

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

Explicitly states 'Use to modify content, tags, importance, or visibility of a node,' giving a clear condition for use. However, it does not mention when not to use the tool or name alternative tools, so it stops short of a 5.

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

Deploy Server