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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_update

Update a memory node’s content, layer, tags, aliases, or importance, and use override:true when reducing or removing hard protection to keep the cognitive graph accurate.

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
aliasesNo
contentNo
projectNo
overrideNo解除/降低硬保护或降级受保护层时必须为 true
protectedNo
importanceNo
confirmedByNo
importanceSourceNo
rejection_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • addedInput schema / properties / aliases
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / confirmedBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / importanceSource
      Added value: +{
      +  "enum": [
      +    "hint",
      +    "confirmed"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / override / description
      Previous value: -"解除或降低硬保护时必须为 true"New value: +"解除/降低硬保护或降级受保护层时必须为 true"
    • addedInput schema / properties / project
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / rejection_reason
      Added value: +{
      +  "type": "string"
      +}
  2. 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 must carry the full behavioral load; it does disclose the most important trait, namely that hard-protected nodes reject certain mutations unless override is passed. It omits other consequential behavior for a 13-parameter mutation: whether the update is a partial merge, what happens to unspecified fields, and whether protection state changes are reversible.

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?

A single front-loaded sentence with the mutable fields listed first and the override caveat in parentheses, so the reader hits the core purpose immediately. There is no filler, though the parenthetical packs three distinct override triggers into a dense clause.

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 a 13-parameter mutation tool with no annotations, no output schema, and 15% schema coverage, the definition is too thin. Critical semantics for protected, confirmedBy, importanceSource, and rejection_reason, plus merge behavior and failure modes, are left undocumented anywhere.

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 15%, so the description needs to compensate and largely does not. It names content, layer, tags, aliases, importance, and the override condition, but says nothing about protected, confirmedBy, importanceSource, rejection_reason, project, or title, which are exactly the ambiguous parameters an agent would need explained.

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 gives a specific verb ('更新') plus the resource ('记忆节点') and enumerates the mutable facets (内容、层级、标签、别名、重要度), so an agent knows exactly what the tool changes. It stops short of naming a sibling such as cg_write or cg_link to draw the create-vs-modify boundary, so it is clear but not fully differentiated.

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?

One genuine conditional is stated: hard-protected nodes need override: true when lowering importance, migrating out of a protected layer, or removing protection. Beyond that the definition gives no guidance on when to choose cg_update over cg_write, cg_link, or cg_forget, leaving the primary routing decision implied.

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