Skip to main content
Glama

Calculate an ISO 6346 check digit

bpj_container_code_check
Read-onlyIdempotent

Calculate a freight container check digit from the owner prefix, category and six-digit serial.

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": {
      "value": "<value>"
    },
    "name": "bpj_container_code_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered and the bar is lower. Beyond that the description adds nothing: it does not say whether an invalid payload raises an error, returns a failure flag, or returns the digit alongside a validity verdict. It also describes the input as three separate components while the schema actually takes a single opaque string, leaving the call shape unexplained.

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 filler, and the standard and resource come first. It is efficiently written, though the brevity edges into under-specification rather than trimming redundancy.

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?

No output schema exists, so the description should indicate what comes back, and it does not — the agent cannot tell whether the result is a bare digit, a full code, or a validity boolean. Combined with the unresolved single-string-versus-three-components mismatch and zero schema coverage, there are real gaps for a tool this simple.

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% and the sole parameter is an opaque 'value' string capped at 240 characters, so the description must carry the load. It partially compensates by naming the semantic parts — owner prefix, category, six-digit serial — but never says how they are combined into one string (concatenated like 'MSCU1234567', space-separated, or otherwise). An agent still cannot construct a valid call from the description alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource — 'Calculate a freight container check digit' — pinned to the ISO 6346 standard named in the title. It is instantly separable from the sibling check-digit calculators (CUSIP, IMEI, ISSN, VIN) because the resource is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the resource name: an agent can infer this is for freight container numbers rather than CUSIPs or IMEIs. There is no explicit statement of when to reach for this versus another check-digit tool, and no guidance on preconditions such as input validation or what to do when a number fails the check.

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.