Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_status

Read-onlyIdempotent

Check connection health and session statistics for a serial session to diagnose link issues and monitor active UART connections.

Instructions

Return connection health and session statistics.

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

Input Schema

NameRequiredDescriptionDefault
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds nothing about the behavior that matters here: what is returned when session_id is omitted (all sessions? default session? error?), and what 'health' means operationally.

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?

A single front-loaded sentence with no filler. It is efficient, though efficiency here comes partly at the cost of the missing details rather than deliberate compression of rich content.

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?

No output schema exists, so the description carries the burden of explaining return values, and 'connection health and session statistics' is too vague to act on. Combined with the undocumented optional parameter and no default semantics, an agent cannot reliably predict the response.

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?

The schema documents zero parameters (0% coverage) and the single optional session_id has no description anywhere. The description never mentions session_id or explains the omitting-behavior, so the agent cannot infer the scope of the call.

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 ('Return') and a specific resource ('connection health and session statistics'), so an agent can tell it is a diagnostics read. It does not distinguish itself from siblings like serial_list_sessions or serial_get_signals, which overlap conceptually.

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 statement of when to use this versus serial_list_sessions (session inventory) or serial_get_signals (line-level signal state). With 24 siblings, the absence of any routing guidance leaves the agent to guess.

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