Skip to main content
Glama

Compute Fletcher-16

bpj_fletcher16
Read-onlyIdempotent

Compute the two modulo-255 running sums and assemble a Fletcher-16 checksum.

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

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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. Beyond that the description only restates the algorithm's definition and says nothing about how invalid hex input is treated, what the output representation is, or limits such as the 3000-character input cap.

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 front-loaded sentence with no filler; every clause carries meaning and nothing is padded.

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

Completeness2/5

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

For a standalone hashing utility with no output schema and an undocumented parameter, the description should specify input encoding and output form (hex width, integer vs string). It leaves both unstated, so an agent cannot predict what comes back.

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% for the single 'bytes' parameter, so the description carries the burden but never mentions the input at all. The only hint that input is hex-encoded comes from the schema's own title, and the description adds no encoding, case, length or formatting guidance.

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 and resource (compute a Fletcher-16 checksum) and adds algorithm detail about the two modulo-255 running sums. It does not distinguish itself from the near-identical sibling bpj_adler32, so an agent must already know which checksum it wants.

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 Fletcher-16 over the many other checksums in the catalog, no preconditions, and no exclusions. The agent gets the semantics of the algorithm but no routing guidance.

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.