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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_recall

Retrieve and reinforce relevant memory nodes using keyword, layer, and tidal-weighted search; automatically combines FTS5 and vector semantic recall when an Embedding API is configured.

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可选:限定检索层级
includeExpiredNo是否包含已过期记忆,默认 false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden, and it does disclose two non-obvious traits: automatic hybrid FTS5+vector recall when an Embedding API is configured, and that hit nodes get strengthened ('强化命中节点'), i.e. a read-looking tool mutates state. It still omits the result shape, the meaning of 'tidal weighting', and any cost/side-effect magnitude for the reinforcement.

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: verb, resource, mechanism, then the side effect appended. Dense but nothing is redundant for the size of 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?

The definition covers retrieval mechanics and the reinforcement side effect, which is what an agent most needs to know before calling. However, with 4 parameters, no annotations, and no output schema, the agent is left guessing what a returned memory record looks like and how limit interacts with layer filtering.

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 all four parameters (query, limit, layers, includeExpired) are already documented in the schema. The description's mention of keyword and layers restates rather than extends that, and it adds no semantics for limit or includeExpired. 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?

Names a specific verb and resource ('检索记忆' – retrieve memories) plus the retrieval dimensions (keyword, layer, tidal weighting) and the hybrid FTS5+vector mechanism. An agent can tell this is the memory search/recall entry point rather than a write (cg_write) or stats tool, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative such as cg_read or cg_reflect. The only conditional statement is internal to the tool ('若已配置 Embedding API…'), which explains behavior rather than tool selection.

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