Skip to main content
Glama

send

Transmit exact text or control characters to a shared COM port immediately, with no implicit newline and no lease or takeover needed.

Instructions

Immediately send exact text/control characters (no implicit newline). No lease or takeover required.

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>",
      "text": "<text>"
    },
    "name": "send"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
textYes
encodingNoutf-8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure; it does disclose immediacy, exactness without an implicit newline, and no lease/takeover requirement. It leaves out failure behavior, blocking semantics, and whether the target port must already be open.

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?

Two short sentences with no filler, and the operational constraints are front-loaded. The parenthetical and second sentence each add useful information.

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 three-parameter write tool with no annotations and no output schema, the description covers key sending semantics but omits the port prerequisite and encoding/return behavior. It is adequate but incomplete for a no-annotation mutation tool.

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%, so the description must explain the three parameters. It clarifies 'text' (exact characters, no implicit newline) but never explains 'port' or the 'encoding' default, leaving key parameter meaning undocumented.

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 uses a specific verb, 'send', with the resource 'exact text/control characters', and adds that no newline is appended. It implicitly distinguishes itself from send_bytes by focusing on text/control characters, though it does not name the sibling.

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?

It implies use for sending text/control characters and notes that no lease or takeover is required, giving a prerequisite condition. However, it does not explicitly say when to prefer this over send_bytes or whether the port must already be open.

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