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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_import_vault

Imports historical Markdown notes from an external directory into the cognitive graph in strictly read-only mode, supporting standard Frontmatter, Obsidian Vault, and DSH mdcg formats.

Instructions

以严格只读方式从外部 Markdown 目录(兼容标准 Frontmatter、Obsidian Vault 与 DSH mdcg)导入历史笔记到蓝汐认知图谱。

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": {
      "sourceDir": "<sourceDir>"
    },
    "name": "cg_import_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceDirYes待导入目录的绝对路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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, and it does useful work by declaring the source directory is accessed in strict read-only mode ("以严格只读方式"). It still omits important behavior for a bulk ingest operation: whether existing nodes are overwritten, how duplicates/conflicts are handled, whether the import is idempotent, and any size or rate limits.

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 dense sentence with the read-only guarantee and the resource front-loaded, and no filler. It is efficient, though the parenthetical format list slightly crowds the sentence's core claim.

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 one-parameter tool with no output schema the description covers the essential what and where. It falls short on conflict/duplicate handling and the absence of any output description matters because there is no output schema to fill that in, so an agent cannot predict the result of an import.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines it as an absolute path. The description adds context about what kind of directory is acceptable (Frontmatter/Obsidian/DSH mdcg layouts) but no format details beyond that, so it lands at the baseline for fully-covered schemas.

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+resource pair: importing historical notes from an external Markdown directory into the 蓝汐认知图谱. It also enumerates supported source formats (standard Frontmatter, Obsidian Vault, DSH mdcg), which tells an agent the input shape. It does not explicitly contrast with cg_read/cg_write, but the bulk external-directory import scope is clearly distinct.

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 rather than stated: the description makes clear this is for ingesting an existing external Markdown corpus, which distinguishes it from in-graph operations. However, it gives no explicit when-to-use versus when-not guidance, no prerequisites (permissions, target graph state), and no note on when to prefer an in-graph tool such as cg_write instead.

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