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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_read

Reads a memory node by ID, returning complete details, tidal retention score, incoming and outgoing edge relationships, and its on-disk file path.

Instructions

按节点 ID 读取完整记忆详情、潮汐保留度、出入边关系与磁盘文件路径。

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes记忆节点 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 discloses the return surface (retention score, edge relationships, file path), which usefully signals this is a read operation, but it says nothing about error behavior for unknown IDs, permission requirements, or whether reading affects the tidal retention score it exposes.

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?

One front-loaded sentence with the verb and the ID-based lookup first, followed by the returned fields. No filler, though the enumerated return list is dense and would read better as structured clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema and no annotations, the description covers both the input basis (node ID) and the main return components, which is close to sufficient. The remaining gap is failure/edge-case behavior, which matters less for a pure read.

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% and the single parameter 'id' is already documented as '记忆节点 ID'. The description restates the same meaning (read by node ID) without adding format, source, or lookup guidance, 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?

States a specific verb (read) and resource (memory node by ID) plus the exact payload returned: details, tidal retention score, in/out edges, and on-disk file path. That is enough to separate it from retrieval-style siblings such as cg_recall, though it does not explicitly name them.

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 only implied by '按节点 ID' — an agent can infer this is the direct-fetch path once it already holds a node ID, as opposed to a search-style retrieval. There is no explicit when-to-use/when-not statement, no note on what to do if the ID is unknown, and no routing to an alternative tool.

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