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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_stats

Retrieve cognitive graph runtime overview, tidal water level distribution, per-layer node counts, disk truth-source freshness (dataStale), and masked configuration, giving a quick health snapshot for memory graph monitoring.

Instructions

获取蓝汐(Lanxi)认知图谱运行概览、潮汐水位分布、各层节点统计、磁盘真源新鲜度检测(dataStale)与配置(密钥已脱敏)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 must carry the safety profile, and it does partially: the enumerated content is clearly read-only observation, and it notes that configuration keys are redacted (masked), which is meaningful security context. It does not state cost, size, whether results are cached, or how freshness is computed beyond the 'dataStale' label.

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?

One front-loaded sentence with the purpose stated first, followed by a compact enumeration of returned categories; no filler or repetition. The trailing parentheticals (dataStale, keys redacted) are high-value qualifiers rather than noise.

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?

There is no output schema, so listing the five data categories is exactly what the description needs to do to set return expectations. Combined with zero parameters, the definition is close to self-sufficient; only return size/format and usage triggers remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema already shows. The baseline of 4 applies, and the description sensibly spends its space on output content rather than nonexistent inputs.

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: fetch a consolidated stats/diagnostics snapshot of the Lanxi cognitive graph, then enumerates the exact categories (runtime overview, tide-level distribution, per-layer node counts, dataStale freshness, redacted config). This lets an agent tell it apart from read/link/goal verbs in the sibling set. It stops short of explicitly contrasting itself with the closest sibling, cg_graph, which also deals with graph structure.

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: nothing says whether to call this before maintenance, to diagnose stale data, or instead of cg_graph for structural questions. The categories imply a health-check/diagnostic role, but the agent must infer that entirely.

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