Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_read_since

Read-onlyIdempotent

Read serial history without consuming it, returning the newest bytes up to a byte limit so you can inspect recent device output while preserving the stream.

Instructions

Read history without consuming it, returning the newest bytes up to the limit.

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_read_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
encodingNoutf-8
session_idNo
max_output_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / max_output_bytes
      Added value: +{
      +  "default": 16384,
      +  "title": "Max Output Bytes",
      +  "type": "integer"
      +}
  2. First observedv0.6.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds important context beyond them: the history is not consumed, and the return is bounded to the newest bytes up to a limit. It still does not explain how the 'since' cursor affects results or whether truncation occurs.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted words. It is efficiently structured, though its brevity leaves important gaps that are better captured under completeness.

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 tool with four undocumented parameters and no output schema, the description is too thin. It conveys the non-consuming read behavior but fails to explain the meaning of 'since', session scoping, encoding, or how the byte limit interacts with the returned data.

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 description coverage is 0% for four parameters, so the description must compensate. It only indirectly references 'max_output_bytes' via 'up to the limit' and says nothing about 'since', 'session_id', or 'encoding', leaving the central cursor parameter unexplained.

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 states a specific verb and resource: reading serial history, with the key nuance that it does not consume the history, and returns newest bytes up to a limit. It implicitly distinguishes itself from a consuming read but does not name any sibling tool.

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?

The phrase 'without consuming it' implies the intended use case: non-destructive history reads. However, it gives no explicit guidance on when to choose this over serial_read, serial_read_hex, or other sibling tools, nor does it mention prerequisites such as an active session.

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