cog-brain

Official

Overview Schema Source Related Servers Discussions Admin

vault_status

Check index health before trusting search results: see notes on disk versus indexed, last index run, and notes changed since. Detects stale indexes after manual edits.

Instructions

Index health: notes on disk vs indexed, when the index last ran, and which notes changed since.

Call this before trusting a search result: after a write the index is refreshed automatically, but a manual file edit from outside this server leaves it stale.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the index-refresh behavior (writes auto-refresh, external edits leave it stale), which is genuine context beyond the tool's output. It does not state read-only/safety profile or any permission/rate constraints, keeping it out of 5 territory.

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?

Front-loaded with the core definition ('Index health: ...') followed by tightly relevant usage context. Two short blocks with no padding, though the second paragraph blends usage guidance with behavioral detail.

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?

An output schema exists, so return values need no elaboration, and with zero parameters the schema gap is nil. The description supplies purpose and the key staleness caveat, making it complete enough to call correctly.

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 the schema cannot carry semantic weight; baseline is 4. Nothing in the description misrepresents the empty argument set.

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?

States a specific resource and scope: reports index health, specifically notes on disk vs indexed, last run time, and which notes changed. This clearly distinguishes it from search/read siblings, though it does not name a specific sibling it differs from (e.g. index_now) to reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit condition for use: 'Call this before trusting a search result,' tied to the trigger of an external manual file edit leaving the index stale. Lacks an explicit pointer to the remediation sibling (index_now) for when the index is stale, so it stops short of a 5.

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

Deploy Server