Skip to main content
Glama

Clear Terminal History

clear_history

Remove captured terminal command logs to manage storage and maintain privacy in the Terminal Reader MCP environment.

Instructions

Clear the captured terminal history log file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:253-278 (registration)
    Registers the 'clear_history' MCP tool with title, description, empty input schema, and inline handler function.
    server.registerTool(
      'clear_history',
      {
        title: 'Clear Terminal History',
        description: 'Clear the captured terminal history log file.',
        inputSchema: {},
      },
      async () => {
        try {
          writeFileSync(LOG_FILE, '');
          return {
            content: [{
              type: 'text',
              text: 'Terminal history cleared.',
            }],
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Failed to clear history: ${error.message}`,
            }],
          };
        }
      }
    );
  • The handler function for the 'clear_history' tool. It clears the terminal history log file by overwriting it with an empty string and returns a success or error message in MCP format.
    async () => {
      try {
        writeFileSync(LOG_FILE, '');
        return {
          content: [{
            type: 'text',
            text: 'Terminal history cleared.',
          }],
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Failed to clear history: ${error.message}`,
          }],
        };
      }
    }
  • Schema definition for the 'clear_history' tool, including title, description, and empty input schema (no parameters required).
    {
      title: 'Clear Terminal History',
      description: 'Clear the captured terminal history log file.',
      inputSchema: {},
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Clear') which implies a destructive mutation, but doesn't specify whether this is reversible, requires permissions, affects system performance, or what happens post-execution (e.g., confirmation message, error handling). For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, direct sentence that states the tool's purpose without any fluff or redundancy. It's front-loaded with the key action ('Clear') and efficiently specifies the target. Every word earns its place, making it highly concise and well-structured for quick comprehension.

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

Completeness2/5

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

Given the tool's complexity (a destructive operation with no parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't address critical context such as the effect of clearing (e.g., permanent deletion, system impact), success/failure responses, or safety warnings. For a mutation tool with no structured support, more behavioral details are needed to adequately inform an agent.

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 has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. A baseline of 4 is applied for zero-parameter tools, as the description correctly focuses on the tool's action without unnecessary parameter details.

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 clearly states the action ('Clear') and the target resource ('the captured terminal history log file'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_last_command' or 'search_output', but the verb 'Clear' strongly implies a destructive operation versus their read-only nature, providing some implicit distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether history must exist), exclusions (e.g., irreversible effects), or direct comparisons to siblings like 'get_recent_commands' for viewing history. Usage is implied only by the tool's name and purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrisvin-jabamani/terminal-reader-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server