Skip to main content
Glama

krusch_context_health

Read-onlyIdempotent

Check persistent memory health for a project, including taxonomy counts, storage mode, and 30-day TTL decay, to identify stale or missing context.

Instructions

Operational health check, memory counts by closed taxonomy, storage mode, and 30-day TTL decay review.

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
projectNoTarget project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real value by listing what the report covers (taxonomy counts, storage mode, TTL decay), but it does not say whether the decay review only reports or flags actionable items, nor anything about output shape.

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 dense sentence with no padding, and the most distinctive content (taxonomy counts, TTL decay) is front-loaded. The fragmentary style costs a little clarity about whether the tool performs or merely reports the review.

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 simple (one optional param, fully read-only, no output schema), so the description need not be long, and listing report contents is appropriate. It is still incomplete on default project scoping and on whether the TTL decay review surfaces warnings an agent should act on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single optional parameter at 100% schema description coverage ('Target project'), the schema already does the work, so the 3 baseline applies. The description says nothing about what happens when project is omitted (all projects vs. default scope), which is the one semantic gap the schema cannot fill.

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 (operational health check) and enumerates the concrete contents: memory counts by closed taxonomy, storage mode, and a 30-day TTL decay review. That is enough to distinguish it from the sibling write/read tools (remember, retrieve, revise, nudge), though the telegraphic noun-phrase style never states the verb (reports? returns?) explicitly.

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?

Usage is only implied by the label 'operational health check' – an agent can infer this is the diagnostic/inspection call rather than a data read. There is no explicit when-to-use trigger, no when-not, and no named alternative among the siblings.

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