Skip to main content
Glama
Sign In
BoteX

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find_graph_health

Audit Memory Vault knowledge graph integrity by reporting broken links, orphan notes, and cycles to help maintain accurate workspace memory.

Instructions

Audits Memory Vault knowledge graph integrity: reports broken links, orphan notes, and cycles.

Args:
    workspace_dir: Workspace root directory.
    scope: Lookup scope ('local', 'global', or 'all').

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

Input Schema

NameRequiredDescriptionDefault
scopeNolocal
workspace_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

B3.3/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. 'Audits' and 'reports' imply a read-only inspection, and the description discloses what categories of issues are surfaced, which is useful. However, it does not explicitly confirm read-only behavior, note any permission or performance considerations, or explain how results are structured beyond what the output schema provides.

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?

The description is short and front-loads the purpose before the Args block. Every line contributes, though the Args formatting is slightly mechanical and the scope values could be integrated more naturally.

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?

The tool is a read-only audit with two optional parameters and an output schema, so return values need not be explained. Still, the description lacks guidance on when to use it versus check_health and omits explicit confirmation of its non-destructive behavior, leaving some gaps.

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?

Schema description coverage is 0%, so the description must compensate, and it does so reasonably: it names both parameters and gives the allowed scope values ('local', 'global', or 'all'), which the schema itself does not enumerate. It could go further by explaining default behavior or expected path format, but the core semantics are added.

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 states a specific verb and resource: it 'audits Memory Vault knowledge graph integrity' and enumerates the reported problems (broken links, orphan notes, cycles). It implicitly distinguishes itself from sibling check_health, which is a general health tool, but does not explicitly name or contrast that sibling.

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 guidance on when this tool should be used versus alternatives such as check_health or get_backlinks, and no prerequisites or exclusions are stated. The agent must infer that this is the graph-integrity audit from the name and description alone.

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