Skip to main content
Glama
Sign In
AT Bridge

AT Bridge

by zeng-andrew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

at_open_port

Open a specified COM port and establish a serial connection to debug IoT modules via AT commands.

Instructions

Open the specified COM port and establish a serial connection.

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

Input Schema

NameRequiredDescriptionDefault
portYesSerial port device name. Windows: COM3, COM4, etc.; Linux: /dev/ttyUSB0, /dev/ttyACM0, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. It does not explain what happens if the port is already open, whether the operation blocks, timeout behavior, or required permissions. This is insufficient for a connection-establishing action.

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?

The description is a single, front-loaded sentence of 10 words with no unnecessary words. Every word contributes to the core action, making it highly concise and well-structured.

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?

Given the tool has one parameter and no output schema, the description is minimally adequate. However, it lacks information on success/failure indicators, error conditions, or connection status, leaving gaps in completeness.

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

Parameters3/5

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

There is one parameter 'port' with schema coverage 100% and detailed examples (COM3, /dev/ttyUSB0). The description adds no extra meaning beyond the schema, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Open', the resource 'specified COM port', and the result 'establish a serial connection'. It distinguishes from siblings like at_close_port and at_list_ports by specifying a connection-establishing action.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. For example, it does not say 'before sending commands' or mention prerequisites like port availability. The agent must infer usage context from the tool name alone.

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

Deploy Server

Other Tools