Skip to main content
Glama

knowledge_status

Check the knowledge index's file, chunk, and embedding counts and freshness to verify search data is current and detect stale indexes.

Instructions

Состояние индекса: файлы, чанки, эмбеддинги, свежесть.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full load of behavioral disclosure, yet it only lists the categories of data reported. It never states that the call is read-only, whether it is cheap or slow, whether it can block while indexing runs, or what the response actually looks like.

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 short sentence fragment with the resource front-loaded and a compact list of what is returned. Nothing is wasted, though the fragmentary style omits a verb, which slightly weakens immediate comprehension.

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?

Given a zero-parameter tool with no output schema and no annotations, the description should explain what each reported dimension means and whether the call is a safe read. It covers the content categories but leaves the behavioral side and return shape entirely unspecified.

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. The baseline for a parameterless tool applies, and the description does not mislead about 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 names a specific resource ('Состояние индекса' — the index state) and enumerates what it reports: files, chunks, embeddings, freshness. That lets an agent tell it apart from sibling mutation tools such as knowledge_reindex or knowledge_commit, though the contrast is never stated explicitly.

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 guidance, no indication of how this differs from knowledge_reindex (which presumably changes the index), and no mention of prerequisites or typical call contexts. The only cue is the implied idea of 'checking status', which the agent must infer.

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