Skip to main content
Glama
Sign In
zhiji-memory

zhiji-memory

by xfhxxffhh224
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

zhiji_status

Check the health status and scale of the memory-bridge service, including file count, memory block count, and FTS availability. Diagnose connectivity issues.

Instructions

查询 memory-bridge 服务健康状态与规模(文件数/记忆块数/FTS 可用性)。用于连通性诊断。

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": "zhiji_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, or side effects. For a simple status check, minimal transparency is offered beyond the basic purpose.

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?

The description is a single, concise sentence that efficiently communicates the tool's function and key outputs with no superfluous information.

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?

Given no output schema, the description covers the main return values (health status, file count, etc.). It lacks detail on response format or interpretation, but for a simple status tool it is mostly complete.

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?

With zero parameters, the baseline is 4. The description adds meaning by specifying the output metrics (file count, memory blocks, FTS availability), which compensates for the absence of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries memory-bridge service health status and scale, specifying file count, memory block count, and FTS availability. Its purpose for connectivity diagnosis is explicit, and it distinguishes from sibling tools that handle workspace, search, ingest, etc.

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?

The description implies usage for connectivity diagnosis but does not explicitly state when to use or not use this tool over alternatives. No sibling differentiation or exclusions are provided.

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

Deploy Server

Other Tools