Skip to main content
Glama

henry_reset

Clear all stored analysis findings and reports to reset the analyzer’s in-memory state between unrelated analysis sessions.

Instructions

Clear all stored analysis findings and reports.

Use this to reset the analyzer's in-memory state between unrelated analysis sessions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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. It does disclose the destructive scope ("all stored analysis findings and reports") and frames the state as in-memory, but it never says whether the clear is reversible, whether it requires confirmation, or whether persisted reports are also affected — a real gap for a destructive zero-arg tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the destructive action front-loaded, and the usage note second. No filler or restated title, and every clause carries information.

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?

For a simple zero-parameter tool with an output schema and no annotations, the description covers what is cleared and when to invoke it, which is nearly everything needed. The remaining ambiguity — "stored" versus "in-memory" — leaves the blast radius slightly unclear.

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 has nothing to explain and the baseline of 4 applies. The description adds no parameter detail because none is needed.

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 pairs a specific verb ("Clear") with a specific resource ("all stored analysis findings and reports"), so the agent knows exactly what the tool does. It does not explicitly contrast itself with any sibling, but the reset semantics are plainly distinct from the analyze/explain/inspect/predict siblings.

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?

"Use this to reset the analyzer's in-memory state between unrelated analysis sessions" gives a concrete when-to-use condition tied to session boundaries. It stops short of stating when not to call it (e.g., mid-session) or naming an alternative, but the triggering context is clear.

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