Skip to main content
Glama

port_status

Inspect a shared COM port's state: input mode, active executions, connected terminal clients, RX cursor positions, and disconnect status. Use it to diagnose access or read position issues.

Instructions

Inspect shared input mode, active executions, terminal clients, RX cursors and disconnect state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "port": "<port>"
    },
    "name": "port_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and 'Inspect' does imply a non-mutating read, which is useful. But it says nothing about what happens when the port is closed or unknown, whether the call has side effects on RX cursors, or what the response shape looks like, leaving real behavioral gaps for a state-inspection tool.

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?

One tightly packed sentence with no filler and the resource front-loaded. Slightly list-like phrasing but every noun names a concrete piece of returned state, so nothing is wasted.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, enumerating the returned fields is genuinely helpful. The missing element is the meaning and origin of the 'port' argument, plus any error/edge behavior, which leaves the definition adequate but incomplete.

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% and the single 'port' parameter is unexplained. The description never clarifies whether 'port' is a name, an ID, or a handle from open_port, which is the one piece of meaning the description needed to add over the bare schema.

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 verb 'Inspect' plus an enumerated set of port state fields (shared input mode, active executions, terminal clients, RX cursors, disconnect state) makes clear this is a read-only diagnostics call on a single port. It does not, however, distinguish itself from the sibling list_ports, so an agent must infer that this targets one port while list_ports targets many.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. An agent can only infer that this is the diagnostic call to make before closing or executing against a port, which is implied rather than stated.

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