Skip to main content
Glama

Frame bytes using COBS

bpj_cobs_frame
Read-onlyIdempotent

Encode consistent-overhead byte stuffing and append the terminating zero delimiter.

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_cobs_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: a terminating zero delimiter is appended to the output. It does not say what the returned representation is (hex text vs. raw bytes) or how the 3000-char input cap affects output size.

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?

One sentence, zero filler, and the algorithm and the delimiter behavior are both front-loaded. Nothing could be removed without losing 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?

This is a simple pure transform with full annotation coverage, so the bar is low and the description is nearly adequate. The one real gap is that it never says what comes back — presumably a hex string with a trailing 00 — and there is no output schema to fall back on. For a one-parameter encoder that is a minor but real omission rather than a serious deficiency.

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

Parameters4/5

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

With a single required parameter the schema does most of the work: the property is titled "Hexadecimal bytes" with a maxLength, so format and limits are discoverable structurally. The description contributes nothing extra about the parameter, but at one param and a self-describing schema the baseline of 4 is appropriate.

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 ("Encode") and names the exact algorithm (consistent-overhead byte stuffing, i.e. COBS), plus the terminating-zero append. That is far more identifying than the vague "frame" in the title and separates it from framing siblings like bpj_slip_frame. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4.

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 statement of when to choose COBS framing over an alternative framing scheme, no prerequisite context, and no exclusions. The agent must infer applicability entirely from the algorithm name.

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.