Skip to main content
Glama

Frame bytes using SLIP

bpj_slip_frame
Read-onlyIdempotent

Escape the SLIP END and ESC bytes and surround the serial frame with END delimiters.

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": {
      "bytes": "<bytes>"
    },
    "name": "bpj_slip_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, but the description adds useful behavioral detail: it specifies which bytes are escaped and that END delimiters surround the frame. It does not state the output representation, which matters because there is no output schema.

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 definition is a single front-loaded sentence with no wasted wording. It efficiently describes the transformation before mentioning framing details.

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 simple pure transformation with annotations covering safety, the description explains the core SLIP operation adequately. However, it omits the hexadecimal input encoding and the output representation, both important because there is no output schema and schema description coverage is absent.

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?

There is one required parameter, but schema description coverage is 0%; the description does not mention that input must be a hexadecimal string or that it is capped at 3000 characters. It says 'bytes' generically, which adds little beyond the parameter name and title already in the 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 description uses a specific verb and resource: it names escaping the SLIP END and ESC bytes and surrounding the frame with END delimiters. This is clear and operational, but it does not explicitly differentiate the tool from framing alternatives present in sibling names such as bpj_cobs_frame.

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 states only what the tool does, with no explicit when-to-use or when-not-to-use guidance. Given a sibling like bpj_cobs_frame, an agent receives no guidance about choosing SLIP framing over COBS framing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.