Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_clear_history

DestructiveIdempotent

Clears the stored receive history for a serial session, letting you reset the buffer and inspect only new incoming data.

Instructions

Clear a session's receive history.

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

Input Schema

NameRequiredDescriptionDefault
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description does add value by specifying what is destroyed — the receive history — rather than vague 'clear'. However, it says nothing about whether the cleared data is recoverable, whether the session is otherwise reset, or how the operation behaves while a read is in flight.

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?

One front-loaded sentence with zero filler. Nothing redundant, nothing buried.

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?

For a destructive, idempotent single-parameter tool with no output schema, the key missing piece is the semantics of the optional session_id default and any effect on concurrent readers. Annotations cover safety but not that behavior, so the description leaves a real gap.

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

Parameters2/5

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

Schema coverage is 0% and the single session_id parameter is nullable with default null, yet the description never explains what a null session_id means (current session? all sessions?). For a tool whose only parameter is undocumented everywhere, the description should have compensated and does not.

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?

States a specific verb+resource: clearing a session's receive history. It distinguishes the operation from siblings like serial_read or serial_read_since, which consume rather than erase history. No explicit sibling routing, but the intent is unambiguous.

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?

There is no guidance on when to call this versus serial_read_since (which also deals with history) or when it is appropriate to reset a buffer. No preconditions, no warnings about timing relative to reads.

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