Skip to main content
Glama

send_bytes

Sends exact base64-encoded bytes immediately without resetting, flushing, or retrying. Use for precise data transmission over a shared serial port.

Instructions

Immediately send exact base64-encoded bytes. No lease; never resets, flushes or retries automatically.

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>",
      "base64_data": "<base64_data>"
    },
    "name": "send_bytes"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
base64_dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful traits: immediate delivery, no lease acquisition, and no automatic reset, flush, or retry. It omits prerequisites (e.g. whether the port must already be open via open_port) and what happens on write failure, leaving some behavioral gaps.

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 compact sentences, front-loaded with the action and its format, followed by the key behavioral caveats. No filler or redundancy.

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 two-parameter write tool with no annotations and no output schema, the description covers data format and delivery semantics but leaves the port parameter, preconditions, and failure/return behavior undocumented. Adequate but with clear gaps.

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?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'base64_data' must be exact base64-encoded bytes, which adds real meaning, but says nothing about 'port' — its format, whether it must be opened first, or how it is identified.

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 and resource ('send exact base64-encoded bytes') plus the immediacy constraint, which clearly separates it from the sibling 'send' that presumably holds a lease. It never names the alternative explicitly, so differentiation is inferred rather than stated.

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?

'No lease; never resets, flushes or retries automatically' implies this is the low-level raw-write path versus a higher-level 'send', but no sentence says when to choose this tool over 'send' or 'execute'. Usage must be inferred from the behavioral negatives.

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