Skip to main content
Glama

krusch_context_health

Read-onlyIdempotent

Inspect memory store statistics and INV-12 span-grounded drift counts to check memory health and flag invariant drift.

Instructions

Inspect memory store statistics and INV-12 span-grounded drift counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safe-read profile is fully covered by structured data. The description adds nothing beyond that restatement — it does not say what statistics are returned, whether the call is cheap or expensive, or what a drift count even represents. With no output schema, this is a real gap.

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 front-loaded sentence with no filler or padding. Its only weakness is that the second clause ('INV-12 span-grounded drift counts') spends words on unexplained internal terminology rather than conveying meaning.

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?

With no parameters that is adequate, but the absence of an output schema means the description is the only place an agent can learn what comes back, and 'statistics and drift counts' is too vague to act on. It is minimally sufficient for deciding to call the tool but not for interpreting the result.

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 baseline is 4; there are no argument semantics the description needs to compensate for. The schema is empty and requires no explanation.

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?

"Inspect memory store statistics and INV-12 span-grounded drift counts" names a specific verb (inspect) and two concrete resources, making it distinguishable from siblings like krusch_context_remember or krusch_context_retrieve. The 'INV-12 span-grounded drift counts' phrase is opaque jargon that an agent cannot decode, which keeps it below 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 Guidelines2/5

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

The description gives no when-to-use guidance and names no alternatives or conditions that select this tool over krusch_context_nudge or krusch_stack_status. An agent must infer from the name alone that this is a diagnostic/health-check call.

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