Skip to main content
Glama
蓝汐 · 潮汐认知图谱

蓝汐 · 潮汐认知图谱

by A16Nights

cg_update

Update a memory node's content, layer, tags, title, importance, or protection status; pass override when lowering importance or removing hard protection.

Instructions

更新记忆节点内容、层级、标签或重要度(若节点受硬保护,降低重要度或解除保护需传 override: true)。

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": "cg_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes记忆节点 ID
tagsNo
layerNo
titleNo
contentNo
overrideNo解除或降低硬保护时必须为 true
protectedNo
importanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the hard-protection safeguard and override requirement, but leaves partial-update semantics, treatment of omitted fields, failure behavior, and other mutation consequences unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is compact, front-loads the operation, and isolates the protection exception clearly in parentheses. It contains no filler, although its brevity contributes to several important parameters remaining unexplained.

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 an eight-parameter mutation tool with no annotations or output schema and only 25% schema coverage, the definition is insufficiently complete. The override warning is helpful, but basic update semantics, field constraints, protected/title behavior, and error or result expectations remain unclear.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description needs to compensate substantially. It lists several editable fields and clarifies override, but does not explain title, protected, importance constraints, layer enum meanings, or whether supplied tags and content replace or merge with existing values.

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 states a specific action and resource: updating a memory node's content, layer, tags, or importance. It does not distinguish the tool from siblings, and its field list omits the schema's title and protected parameters.

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 wording implies use for modifying an existing memory node, and the parenthetical gives an explicit condition for using override on protected changes. It provides no broader tool-selection guidance, alternatives, or circumstances in which another operation should be used.

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