Skip to main content
Glama

Run-length groups for bytes

bpj_rle_byte_runs
Read-onlyIdempotent

Group consecutive identical octets into value and repetition count pairs.

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

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value by revealing the output shape (value/count pairs), which matters since there is no output schema, but says nothing about ordering, handling of empty input, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted wording. The only weakness is jargon ('octets' rather than bytes) that adds ambiguity rather than precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only, non-destructive transformation with no output schema, the description plus annotations cover most of what an agent needs, including the return shape. The one substantive hole is the unstated hexadecimal encoding of the input.

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 description coverage is 0%, so the description carries the burden of explaining the single parameter, yet it never states that 'bytes' is supplied as a hexadecimal string (that only appears in the schema title). Mentioning 'octets' hints at byte semantics but leaves the hex encoding and the 3000-character limit unaddressed.

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?

Names a specific verb ('Group') and resource ('consecutive identical octets') and describes the resulting value/count pairs. It does not explicitly distinguish itself from similarly named run-length siblings such as bpj_punctuation_runs or bpj_series_constant_runs, so it falls short of a 5.

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 contains no guidance on when to use this tool, when not to, or which sibling to prefer for alternative run-grouping needs. The agent must infer the use case purely from the purpose sentence.

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.