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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_maintain

Inspect the memory maintenance queue and perform graph upkeep: promote or reinforce nodes, consolidate source memories, backfill embeddings, and rebuild indexes.

Instructions

潮汐维护:查看维护队列(queue),晋升情景(promote),强化访问(touch),手动或 AI 智能凝结(consolidate / ai_consolidate),补全向量(backfill_embeddings),或重建索引(rebuild)。

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

Input Schema

NameRequiredDescriptionDefault
idNopromote/touch 时的目标节点 ID
opNo默认 queue
limitNobackfill_embeddings 批量上限,默认 50
titleNoconsolidate 新节点标题
commitNoai_consolidate 时是否直接写入落盘,默认 false 仅预览草稿
summaryNoconsolidate 提炼后的摘要正文
sourceIdsNoconsolidate / ai_consolidate 的源节点 ID 列表
targetLayerNopromote/consolidate 目标层
archiveSourcesNo凝结后是否归档非保护源节点

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does not meet it. It discloses nothing about mutations: consolidate creates a new node, archiveSources can archive source nodes, and commit writes to storage rather than previewing. None of these effects, nor any permission or destructive-behavior warning, appear in the description.

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 compact sentence that front-loads the domain (潮汐维护) and then enumerates operations in a scannable list. Nothing is wasted, though the density of enumerated ops in one line makes it more of an index than an explanation.

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?

This is a nine-parameter, seven-operation multiplexed tool with no annotations and no output schema, so the description should do more. It lists what the ops are but never explains which parameters pair with which op or what the default queue operation returns, leaving real gaps for a tool of this complexity.

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?

Schema description coverage is 100%, so every parameter including the commit preview/write distinction and the backfill limit is already documented in the schema. The description adds only the op vocabulary, which the enum already provides, so the baseline 3 applies.

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 names a specific maintenance capability and enumerates the seven operations (queue, promote, touch, consolidate/ai_consolidate, backfill_embeddings, rebuild), which map one-to-one onto the op enum. That makes the tool's scope identifiable, though it never contrasts itself with write/update siblings, so the boundary with cg_write or cg_update is left to inference.

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?

Usage is implied by the op list — an agent can guess that 'queue' inspects and 'rebuild' rebuilds — but there is no explicit when-to-use guidance, no statement of which parameters each op requires, and no exclusions relative to siblings. It is enough to route roughly, not to choose confidently.

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