Skip to main content
Glama

Count set bits in bytes

bpj_byte_popcount
Read-onlyIdempotent

Count set bits per byte and across the entire binary payload.

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

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, so the safety profile is covered. The description adds the useful detail that results are reported both per-byte and as a total, but says nothing about the return structure or how input encoding is handled.

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?

A single front-loaded sentence with no redundant or filler wording; the key distinction (per byte plus total) appears immediately.

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 one-parameter pure computation, the description adequately implies the output shape (per-byte counts and an aggregate) and the annotations cover safety. The unresolved input-format ambiguity ('binary payload' vs hex string) is the main completeness gap.

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?

With schema description coverage at 0% and one parameter, the description carries the burden and does not meet it: it says 'binary payload' where the schema title indicates a hexadecimal string, and adds no clarity on encoding, case, or the 3000-character limit.

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 ('Count set bits') and clarifies the two aggregation levels ('per byte and across the entire binary payload'), which meaningfully distinguishes it from neighbors like bpj_utf8_byte_histogram or bpj_rle_byte_runs. It stops short of naming a sibling or explicitly contrasting behavior.

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 when-to-use context, no prerequisites, and no exclusions pointing at alternatives. Usage must be inferred entirely from the operation 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.