Skip to main content
Glama

Calculate an IMEI check digit

bpj_imei_check_digit
Read-onlyIdempotent

Calculate the Luhn check digit of a fourteen-digit device identifier body.

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

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 the safety profile is fully covered. The description adds only that the computation is Luhn-based on a 14-digit body; it says nothing about what is returned (a single digit?), or what happens with non-numeric, wrong-length, or malformed input.

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 zero filler; the verb and the input constraint appear immediately. Nothing in it could be removed without losing information.

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?

For a one-parameter, side-effect-free computation with full annotation coverage and no output schema, the definition is nearly sufficient. The remaining gap is that the return value (the check digit itself) is only implied rather than stated, which leaves the agent guessing at the result shape.

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?

Schema description coverage is 0% and the single parameter is a generically named "value" with only maxLength 240, so the schema gives the agent almost nothing. The description compensates partially by specifying the expected payload is a fourteen-digit device identifier body, but it does not clarify the character set, whether separators are tolerated, or the failure mode for invalid input.

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?

The description pairs a specific verb ("Calculate") with a specific resource ("the Luhn check digit of a fourteen-digit device identifier body"). The 14-digit/device-identifier framing differentiates it from the sibling check-digit utilities (CUSIP, ISSN, CAS registry) without needing to name them. It stops short of 5 only because the term IMEI itself appears in the title rather than the description.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only hint about correct invocation is implicit in "fourteen-digit ... body," which the agent must infer means passing the partial identifier rather than a full 15-digit IMEI.

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.