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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_recall

Retrieve long-term memory nodes by keyword, layer, and project using hybrid full-text and semantic recall with tidal weighting, and reinforce matched nodes.

Instructions

按关键词、分层、项目与潮汐加权检索记忆(若已配置 Embedding API 则自动执行 FTS5 + 向量语义混合召回),并强化命中节点。

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数,默认 8
queryYes中文或英文检索关键词
layersNo可选:限定检索层级
projectNo可选:项目名称,优先加权匹配该项目记忆(不漏出跨项目记忆)
strictProjectNo为 true 时严格只返回匹配 project 的记忆,默认 false
includeExpiredNo是否包含已过期记忆,默认 false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "可选:项目名称,优先加权匹配该项目记忆(不漏出跨项目记忆)",
      +  "type": "string"
      +}
    • addedInput schema / properties / strictProject
      Added value: +{
      +  "description": "为 true 时严格只返回匹配 project 的记忆,默认 false",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that hybrid FTS5/vector recall activates only when an Embedding API is configured, and that hit nodes are reinforced, but it does not clarify what '强化命中节点' (strengthens hit nodes) means operationally, whether the tool mutates stored memory strength, or what permissions and side effects apply.

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?

The definition is a single, front-loaded sentence that packs the core purpose, optional hybrid-retrieval condition, and side effect without redundant wording. It is appropriately sized for the tool.

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?

For a six-parameter retrieval tool with no annotations and no output schema, the description covers the retrieval approach and a side effect, but it omits guidance on choosing this tool, details about the reinforcement side effect, and any indication of return shape or result ordering. It is adequate but leaves clear gaps.

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 is already documented in the input schema. The description mentions keyword, layer, and project dimensions but adds no syntax or semantic detail beyond the schema, making 3 the appropriate baseline.

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 verb and resource: '按关键词、分层、项目与潮汐加权检索记忆' (retrieve memories by keyword, layer, project, and tidal weighting). This clearly distinguishes it as a search/recall tool, but it does not explicitly contrast it with siblings such as cg_read or cg_graph, so it falls short of a 5.

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?

The description explains the retrieval mechanics and a conditional hybrid-recall behavior, but it does not say when an agent should choose cg_recall over alternatives like cg_read, cg_graph, or cg_reflect. There are no when-to-use or when-not-to-use instructions.

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