Skip to main content
Glama

Compute Adler-32

bpj_adler32
Read-onlyIdempotent

Compute the Adler-32 payload checksum with modulus 65521 and initial value one.

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

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered structur; the description's real contribution is the algorithm constants (modulus 65521, init 1), which guarantee deterministic results. It says nothing about what is returned (integer vs hex string) despite there being 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.

Conciseness4/5

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

One tightly written sentence with the verb and the discriminating constants front-loaded; there is no filler. It is arguably too terse rather than padded, which is a completeness problem rather than a conciseness one.

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 low-complexity, single-parameter, side-effect-free computation this is close to adequate, and the algorithm is fully specified. What is missing is the contract around the call itself: confirmation that the input is a hex string and the shape of the checksum returned.

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?

The single parameter has 0% schema description coverage, so the description must carry the load, and it does not mention the parameter at all. The only hint that input is hex-encoded comes from the schema's title "Hexadecimal bytes", not from the description, and nothing clarifies encoding, padding, or the 3000-char 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?

Names a specific verb ("Compute") and resource ("Adler-32 payload checksum") and pins down the algorithm variant with modulus 65521 and initial value one, so an agent knows exactly which checksum it gets. It does not distinguish itself from any of the many sibling encoding/checksum tools (e.g. bpj_adobe_ascii85, bpj_base58_byte_encoding), which keeps it off 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?

There is no when-to-use or when-not-to-use guidance and no reference to alternatives. The purpose is self-evident from the name for a pure computation, but the description leaves any routing decision entirely to the agent.

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.