Skip to main content
Glama

ie_console_clear

Clears all captured console output records while preserving the continuing ID counter.

Instructions

Forget every record ie_console holds (ids keep counting).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/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 burden. It does disclose the key behaviors: all records are discarded (destructive) and the id counter is not reset, so later ids continue from where they left off — a genuinely non-obvious detail. It does not state that the erasure is irreversible, whether anything is returned on success, or that only console records (not network records) are affected.

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?

A single short sentence with the effect front-loaded and the subtle id-counter caveat in parentheses. Every element earns its place with no filler.

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 zero-parameter, no-output-schema clear operation, the description conveys enough to invoke it correctly and to predict post-clear id behavior. It falls just short of fully complete because irreversibility and the absence of a return value are not stated.

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 no parameters, so there is nothing for the description to disambiguate and the baseline applies. The parenthetical about ids continuing is useful context but is not a parameter concern.

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?

"Forget every record ie_console holds" names a concrete action (erase) and the exact resource (the console record buffer owned by ie_console), so an agent can tell this is the reset counterpart to the ie_console reader. The verb is metaphorical rather than a literal tool-like term such as "clear", but the parenthetical makes the outcome unambiguous.

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 implied rather than stated: an agent can infer this is called to reset console output before reproducing an issue or to avoid re-reading stale entries. No explicit when-to-use condition and no named alternative such as ie_network_clear for network log records are given, leaving scope selection to inference.

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