Skip to main content
Glama

LogNexus State: Clear session state

lognexus_state_clear

Reset persistent agent state to empty when abandoning an issue, switching tasks, or recovering a corrupted state file. This destructive clear drops the entire task contract.

Instructions

Reset the persistent LogNexus agent state to empty. Equivalent to 'lognexus state clear'. Use when abandoning an issue, switching to an unrelated task, or recovering from a corrupted state file. Not for finishing a single subtask (use lognexus_state_finish_task); clearing is destructive and drops the whole contract.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lognexus_state_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key trait: clearing is destructive and drops the whole contract, which warns the agent against casual use. It stops short of stating reversibility, whether any confirmation is required, or what the empty state means for subsequent calls, leaving some behavioral gaps.

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?

Four short sentences, each earning its place: purpose first, then CLI equivalence, then use cases, then the negative case and destructiveness warning. Front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless, annotation-free, output-schema-free tool, the description supplies everything needed to call it safely: what it does, when to use it, when not to, and the destructive consequence. Nothing an agent requires for correct invocation is missing.

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 per the baseline the schema fully covers the calling contract and the description has nothing to compensate for. There is no parameter content the description could add value to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Reset') and resource ('persistent LogNexus agent state to empty'), and explicitly maps itself to the CLI equivalent. It also names the sibling it is not (lognexus_state_finish_task), so an agent can distinguish it from the other state tools without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete triggering conditions — abandoning an issue, switching to an unrelated task, recovering from a corrupted state file — and an explicit exclusion with the correct alternative ('Not for finishing a single subtask (use lognexus_state_finish_task)'). No inference is required to choose between this and its siblings.

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