Skip to main content
Glama

Pack decimal BCD

bpj_packed_bcd
Read-onlyIdempotent

Pack pairs of decimal digits into BCD nibbles with a leading zero for odd lengths.

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": {
      "digits": "<digits>"
    },
    "name": "bpj_packed_bcd"
  }
}

Input Schema

NameRequiredDescriptionDefault
digitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact, the leading-zero pad for odd-length input, which affects output shape. It says nothing about how non-digit characters are handled or what form the packed result takes.

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, front-loaded with the verb and resource, with the padding caveat appended in the right place. Nothing is wasted or buried.

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?

A simple pure transform with rich annotations and no output schema, so little is demanded. Still, the description does not say what the packed result looks like (hex string, byte array, or otherwise), which is the one thing an agent would need to consume the output.

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

Parameters3/5

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

Only one parameter and schema coverage is 0%, so the description must carry weight. It constrains interpretation by saying digits are packed in pairs, implying only decimal digits are valid and any length works, but it never states the max length or rejection behavior for invalid characters.

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 precise verb and resource: packing pairs of decimal digits into BCD nibbles, plus the odd-length padding rule. This is unmistakable against siblings like bpj_adler32 or bpj_base58_byte_encoding, though it does not explicitly contrast with them.

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?

No when-to-use guidance, no prerequisites, and no alternatives or exclusions named. The encoding intent is implied by the description but an agent gets no help deciding between this and other numeric/encoding utilities.

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.