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

蓝汐 · 潮汐认知图谱

by A16Nights

cg_stats

Retrieve cognitive graph runtime overview, tide-level distribution, per-layer node statistics, and configuration details for monitoring and diagnostics.

Instructions

获取蓝汐(Lanxi)认知图谱运行概览、潮汐水位分布、各层节点统计与配置(密钥已脱敏)。

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.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact: credentials in the returned configuration are already masked (密钥已脱敏), which tells the agent output is safe to relay. However it never states that the operation is read-only, gives no indication of cost, freshness, or whether the snapshot is cached, so the safety profile must still be guessed.

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 sentence, front-loaded with the verb and the primary payload (运行概览) before the enumerated sub-sections. There is no filler or hedging. Slight deduction because the tail of the sentence is a comma-separated list of return contents, which reads as inventory rather than as guidance.

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?

With no input schema content, no annotations, and no output schema, the description must itself explain what comes back — and it does, naming four distinct result sections. That is enough for an agent to decide whether to call it. It would be stronger if it noted that the call is side-effect-free, since nothing else in the definition states that.

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, which is the baseline-4 case: there is nothing for the description to disambiguate, and the omission of parameter discussion is correct rather than a gap. The description instead spends its words on what the call yields, which is the right allocation for a no-arg tool.

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 (获取) and enumerates the resource: the Lanxi cognitive graph's runtime overview, tide-level distribution, per-layer node statistics, and configuration. That is far more than a restatement of the name cg_stats. It stops short of 5 because it never contrasts itself with the closest sibling, cg_graph, leaving the agent to infer that this is the aggregate-summary view rather than the raw graph view.

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 the word 概览 (overview) — an agent can infer this is the tool to call when it wants a health/status snapshot rather than a data query. There is no explicit when-to-use statement, no exclusion of alternatives such as cg_graph or cg_maintain, and no prerequisites mentioned. Minimum-viable guidance.

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